Full-depth report · Large modular Java

Spring Boot Architecture Report

This pinned Spring Boot build produces all seven selected chapters: Architecture Overview, Cycle Evidence, Hotspot Risk, Subject Audit, Boundary Review, Current Investigation, and Governance Audit. Matrix limits and dense-figure guards remain visible in the output.

Report packages
1,026
Dependency edges
1,114
Cycle groups
1
Chapters
7
Generation
66.692 s
Case brief

Why this report

At the pinned revision, 261 production class roots become 1,026 report packages. The export records its configured figure limits alongside the deterministic generation basis.

The focused chapters pin spring-boot-build.core.spring-boot.main:org.springframework.boot.context.properties.source. Its 151-node / 121-edge perimeter is materially narrower than the former near-root subject, while the report still combines whole-model orientation, boundary traffic, current investigation context, and governance evidence.

The Cycles Only figure retains the complete four-package SCC: nested containment edges connect boot to bind, source, and env and return env to boot, while architectural dependencies run bind → source → env. Neither edge class closes this particular loop alone.

Selected evidence

  • Global architecture model with Architecture Overview, Cycle Evidence, and Hotspot Risk
  • Subject Audit and Boundary Review for spring-boot-build.core.spring-boot.main:org.springframework.boot.context.properties.source
  • Current Investigation and Governance Audit
  • One compact map per SCC; an additional map only when its focused node-and-edge evidence is a strict superset; top 100 table rows
Generated contents

Read the evidence

The report index is the canonical entry point. These direct chapter links expose the generated reading order without copying or rewriting its findings here.

  1. 01 Architecture OverviewWhole-model report basis, key findings, metric definitions, topology, cycle summary, matrix, composition, and subsystem evidence.
  2. 02 Cycle EvidenceCurrent problem-cycle register, maps, and complementary cycle evidence.
  3. 03 Hotspot RiskBoundary Risk, Visibility Surface, and Internal Tangles subsystem diagrams; Coupling, Visibility, and Abstractness / Instability hotspot rankings; package metrics.
  4. 04 Subject AuditA 151-node focused perimeter with the complete mixed architectural/nested SCC preserved in Cycles Only and in one compact group map; the alternate layout is omitted because it adds no node or edge evidence.
  5. 05 Boundary ReviewIncoming, outgoing, and crossing evidence around the selected source package boundary, with one compact map for its listed four-member problem cycle.
  6. 06 Current InvestigationThe active lens, Current Focus, filters, Heatmap, and visible edges captured for another developer to reopen.
  7. 07 Governance AuditRepository decision evidence and its present structural context.

    This Spring revision has no governance record to inspect. To see an owner-approved decision in its structural context, open the Simple Java Mail example. See Simple Java Mail’s representative Governance Audit

Pinned provenance

Analysis basis and integrity

Source revision
1a5815cf3183a0c9493cece8ba550a6e8b125d67
Licence
Apache-2.0
Analysis source
JVM bytecode from 261 stable production class roots; Java/Kotlin source roots mapped for navigation
Scope
Production modules across the repository; two unstable compiler-output roots excluded
Report selection
Global architecture, Subject Audit, Current Investigation, Governance Audit, compact SCC maps with strict-evidence additional maps, top 100
Generated
2026-07-31T22:30:00Z
Generator
AtlasArc 1.0.1+736db9b9
Output
9 HTML files · 11,146,851 bytes
Portable folder SHA-256
2ba1c56c252f18b5ae1158fde66fb4b41ac846c342436f9e1b3b48a52eefbc01
Structural SHA-256
8799fb5aa661e36f8cb904a26852d0a0ecdd0f828f888213e815b4a1de84a6d3
Generation time
66.692 seconds

Output contract

Generated HTML is unchanged

The report folder is published byte-for-byte. This page supplies context and attribution outside that generated output.

Open pinned source revision
Reproduce the analysis basis
  1. Pin the source

    Check out the recorded Spring Boot revision and keep the working tree clean so AtlasArc can match the report to that exact source revision.

  2. Build stable production output

    Use JDK 21 and the project's Gradle 9.5.0 build. The analyzed owner build supplied 261 stable production class roots and 8,030 compiled classes.

  3. Load the repository model

    Select those production JVM outputs as the Analysis Source. Exclude the two compiler-output roots that do not represent stable production modules.

  4. Choose the full composition

    Select Global architecture model, the recorded org.springframework.boot.context.properties.source subject, Current Investigation, Governance Audit, additional cycle maps, and top 100 rows. The generator keeps one compact map for this four-member SCC and omits the alternate layout because it adds no focused node or edge evidence.

  5. Verify the output

    Generate with AtlasArc 1.0.1+736db9b9, then compare the folder and structural SHA-256 values above before publication.

Read with care

Caveats and safeguards

  • The Printable Version keeps its place

    A colour-coded report route stays in the spare margin on wide screens, follows the current chapter, and prints once beneath the dossier header. It is deliberately absent from standalone chapter files.

  • Large matrices stay guarded

    The whole-model and 132-package focused Matrices exceed the configured 100-package limit, so the report carries explicit Matrix hidden notices instead of shrinking either table below printable legibility. The compact cycle-only Matrix remains present; the export modal exposes the limit and points to a narrower subject or Matrix settings as remediation.

  • The static Sunburst is complete

    The report materializes all 2,301 visible Sunburst arcs under the tested 2,500-arc static-report limit. The lower 350-arc interactive guard remains unchanged; generated report assets are opt-in rather than landing-page payload.

  • Terminal-subject figures are evidence-gated

    The selected source package has no package boundaries below it, so Subject Audit omits inapplicable Subsystems and Composition figures instead of emitting empty canvases. Topology, Cycles Only, the explicit Matrix guard, Hotspots, metrics, boundary evidence, and cycle tables remain present.

  • Headless JVM metric boundary

    The headless acquisition path cannot provide IntelliJ PSI cyclomatic or cognitive complexity. Those metrics are marked unavailable rather than shown as zero.

  • Two outputs were deliberately excluded

    Two compiler-output roots were not stable production modules and were left outside the analysis source. The wrapper discloses that scope choice instead of presenting it as a whole-checkout build count.

  • Pinned, not live

    This report describes the exact source and AtlasArc revisions above. It is not a continuously updated statement about the current Spring Boot main branch.

Source and attribution

Open-source project. Pinned example.

Spring Boot is analyzed from the pinned source revision above under Apache-2.0 . The project name identifies the analyzed open-source snapshot; publication here does not imply affiliation with or endorsement by its maintainers.