Current Investigation Briefing
This report is literal: it captures the active lens, structural intent, focus, and filters rather than generating a whole-model overview.
Visible Dependency Signals
Use these short lists to see which visible dependencies stand apart by reference volume, source concentration, or module crossing. A high value is evidence to inspect; only an unresolved cycle dependency is labelled Problem. The Dependency refs value counts acquired class dependency references aggregated into each package-to-package edge; it is not a source line number.
Highest-reference dependencies
Which visible dependencies carry unusually heavy traffic?
A high reference count means many acquired class dependencies cross this package boundary. Inspect whether that traffic matches the intended design.
Nothing in this report scope is separated enough from its peers to count as a statistical outlier. For orientation, the table shows 5 of the strongest eligible examples.
Continue in AtlasArcReview package boundariesOpen the boundary in Matrix and inspect the exact package-to-package traffic behind these edges.How AtlasArc selected these rows
Rule: Aggregate dependency-reference count is above its upper outlier cutoff.
Population: 864 visible package dependencies with acquired references. Result: No strict outlier result; showing 5 of 864 eligible fallback values.
Cutoff: Dependency refs > 307 (864 eligible values)
| Diagnostic evidence |
|---|
| Sourcespring-boot-build.module.spring-boot-webmvc.mainorg.springframework.boot.webmvc |
| Targetspring-boot-build.core.spring-boot-autoconfigure.mainorg.springframework.boot.autoconfigure |
|
| Sourcespring-boot-build.module.spring-boot-kafka.mainorg.springframework.boot.kafka |
| Targetspring-boot-build.core.spring-boot.mainorg.springframework.boot |
|
| Sourcespring-boot-build.module.spring-boot-http-client.mainorg.springframework.boot.http.client |
| Targetspring-boot-build.core.spring-boot.mainorg.springframework.boot |
|
| Sourcespring-boot-build.module.spring-boot-actuator-autoconfigure.mainorg.springframework.boot.actuate.autoconfigure |
| Targetspring-boot-build.core.spring-boot-autoconfigure.mainorg.springframework.boot.autoconfigure |
|
| Sourcespring-boot-build.module.spring-boot-actuator-autoconfigure.mainorg.springframework.boot.actuate.autoconfigure |
| Targetspring-boot-build.module.spring-boot-actuator.mainorg.springframework.boot.actuate |
|
Concentrated source dependencies
Which sources channel an unusually dominant share of their outgoing traffic into one target?
These rows reveal a source whose strongest dependency absorbs much more traffic than an even split across its visible targets would suggest.
AtlasArc found 4 values clearly separated from their peers in this report scope.
Continue in AtlasArcReview package boundariesOpen this package boundary in Matrix and inspect why one target absorbs so much of the source's visible traffic.How AtlasArc selected these rows
Rule: For each eligible source, its strongest outgoing dependency has reference count at or above the global 75th percentile and dominance over an even target split above its upper outlier cutoff.
Population: 237 sources with at least two visible targets. Result: 4 qualified; showing 4.
Cutoff: Dominance vs even split > 4.27× (237 eligible values)
| Diagnostic evidence |
|---|
| Sourcespring-boot-build.documentation.spring-boot-docs.mainorg.springframework.boot.docs |
| Targetspring-boot-build.core.spring-boot.mainorg.springframework.boot |
|
| Sourcespring-boot-build.module.spring-boot-webmvc.mainorg.springframework.boot.webmvc |
| Targetspring-boot-build.core.spring-boot-autoconfigure.mainorg.springframework.boot.autoconfigure |
|
| Sourcespring-boot-build.module.spring-boot-flyway.mainorg.springframework.boot.flyway |
| Targetspring-boot-build.core.spring-boot.mainorg.springframework.boot |
|
| Sourcespring-boot-build.module.spring-boot-security.mainorg.springframework.boot.security |
| Targetspring-boot-build.core.spring-boot-autoconfigure.mainorg.springframework.boot.autoconfigure |
|
Cross-module dependencies
Which module crossings carry unusually heavy dependency traffic?
These edges cross an explicit module boundary often enough to deserve a check against that module's intended responsibilities.
Nothing in this report scope is separated enough from its peers to count as a statistical outlier. For orientation, the table shows 5 of the strongest eligible examples.
Continue in AtlasArcAudit a module boundaryAudit the selected module boundary and distinguish expected integration from accidental leakage.How AtlasArc selected these rows
Rule: Aggregate dependency-reference count is above its upper outlier cutoff within the cross-module population.
Population: 832 visible dependencies whose endpoints have different known module IDs. Result: No strict outlier result; showing 5 of 832 eligible fallback values.
Cutoff: Dependency refs > 361 (832 eligible values)
| Diagnostic evidence |
|---|
| Sourcespring-boot-build.module.spring-boot-webmvc.mainorg.springframework.boot.webmvc |
| Targetspring-boot-build.core.spring-boot-autoconfigure.mainorg.springframework.boot.autoconfigure |
|
| Sourcespring-boot-build.module.spring-boot-kafka.mainorg.springframework.boot.kafka |
| Targetspring-boot-build.core.spring-boot.mainorg.springframework.boot |
|
| Sourcespring-boot-build.module.spring-boot-http-client.mainorg.springframework.boot.http.client |
| Targetspring-boot-build.core.spring-boot.mainorg.springframework.boot |
|
| Sourcespring-boot-build.module.spring-boot-actuator-autoconfigure.mainorg.springframework.boot.actuate.autoconfigure |
| Targetspring-boot-build.core.spring-boot-autoconfigure.mainorg.springframework.boot.autoconfigure |
|
| Sourcespring-boot-build.module.spring-boot-actuator-autoconfigure.mainorg.springframework.boot.actuate.autoconfigure |
| Targetspring-boot-build.module.spring-boot-actuator.mainorg.springframework.boot.actuate |
|
Structural Map
Topology, cycle-only topology, and Matrix figures show broad packages structure and cycle evidence from complementary angles.
What structure and dependency evidence was active in Topology when this report was submitted?
Problem Cycles
No problem cycles are currently reported.