AtlasArc
Release notes Install free
All showcases

Governance audit · Owner-approved decision

Simple Java Mail Architecture Report

AtlasArc keeps the recorded decision beside the structural evidence it governs. This export includes the global chapters and a Governance Audit that evaluates the owner-approved Intentional package-boundary record against the current graph.

Open generated report Printable Version
Report packages
52
Dependency edges
220
Cycle groups
5
Chapters
4
Generation
19.417 s
Case brief

Why this report

Simple Java Mail carries an owner-supplied Intentional package-boundary record. AtlasArc wrote it through the production governance path, and the Governance Audit evaluates the record as active with its rationale.

The global chapters show topology, Matrix, Composition, cycles, Subsystems, and Hotspots. Governance Audit then lists the decision records and the structural SCC evidence linked to them.

Selected evidence

  • Global Architecture Overview with topology, matrix, and composition evidence
  • Cycle Evidence and Hotspot Risk chapters
  • Governance Audit with the complete repository decision register and present-day structural context
  • 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 basis, topology, matrix, composition, signals, and shared orientation.

    Use Spring Boot's companion overview to see how this same whole-model chapter reads at much larger modular scale. Compare Spring Boot’s large modular Architecture Overview

  2. 02 Cycle EvidenceFive current problem-cycle groups with combined, compact, and matrix views. Alternate group layouts are omitted because they add no focused node or edge evidence.
  3. 03 Hotspot RiskSubsystem and package metric-space evidence for prioritising deeper inspection.
  4. 04 Governance AuditThe decision register, rationale, evaluation state, and present structural context.
Start at report index Open Printable Version
Pinned provenance

Analysis basis and integrity

Source revision
676954dfb8915e144b1737d1cc9bf968d0f874a7
Licence
Apache-2.0
Analysis source
JVM bytecode from 10 production target/classes roots
Governed boundary
org.simplejavamail.email.internal → org.simplejavamail.mailer.internal
Decision
INTENTIONAL · package scope · active
Governance file SHA-256
57217c2ee6b4a6fc4d00e63c1765af3c76df24e256c84c2c7a7b8562ee293546
Report selection
Global architecture, Governance Audit, compact SCC maps with strict-evidence additional maps, top 100
Generated
2026-07-31T22:25:00Z
Generator
AtlasArc 1.0.1+736db9b9
Output
6 HTML files · 5,753,566 bytes
Portable folder SHA-256
62713bb3eee814f0ae54de455b10e7a6462c632d466960e2c171c51722481277
Structural SHA-256
4e0ed75e00d979b3702e1766620314a3a91459fda1c5e951466c8d1e2f2e5187
Generation time
19.417 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 Simple Java Mail revision and produce the ten production target/classes roots with Maven 3.9.10 on JDK 21.

  2. Load the JVM evidence

    Use the production class roots as the bytecode-backed Analysis Source and retain repository scope across the represented modules.

  3. Author the governed decision

    Accept the package-scoped email.internal → mailer.internal boundary as intentional through AtlasArc's governance action, with the project owner's recorded showcase reason.

  4. Choose the governance-led composition

    Select Global architecture model, Governance Audit, additional cycle maps, and top 100 rows. An additional map is emitted only when its focused node-and-edge evidence strictly extends the compact map.

  5. Verify the output

    Generate with AtlasArc 1.0.1+736db9b9 and compare the governance-file, folder, and structural hashes 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.

  • The acceptance is owner-authored

    The intentional record is a manual project-owner decision made for this exact dependency boundary. AtlasArc evaluates and reports that decision; it does not infer architectural intent automatically.

  • Governance-led, not governance-only

    The full global chapters keep the governed decision grounded in representative architecture evidence; Governance Audit remains the reason this composition was selected.

  • Acceptance preserves evidence

    Five cycle groups remain visible in the report model. Governance changes the decision state and adds rationale; it does not erase the underlying structural relationship.

  • Headless JVM metric boundary

    The headless acquisition path marks IntelliJ PSI cyclomatic and cognitive complexity unavailable rather than fabricating zero values.

Source and attribution

Open-source project. Pinned example.

Simple Java Mail 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.

Read the report contract Compare all showcases