Governance audit · Owner-approved decision
Simple Java Mail Architecture Report
The Governance Audit places the owner-approved Intentional package-boundary record beside the dependency evidence it affects. Architecture Overview, Cycle Evidence, and Hotspot Risk provide the wider project context, while the Evidence Appendix supplies capped detailed registers.
- Report packages
- 52
- Dependency edges
- 220
- Cycle groups
- 5
- Chapters
- 5
- Report date
- 31 Jul 2026
Why we included this report
We selected Simple Java Mail as the governance case because its owner approved an Intentional package-boundary decision. Governance Audit places that decision beside its reason and the dependency path it governs.
Architecture Overview, Cycle Evidence, and Hotspot Risk then show the surrounding 52 packages, 220 dependency edges, and five cycle groups before you judge what the accepted boundary means.
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
- Short diagnostic lists that explain why each package or dependency was selected
- Evidence Appendix with at most 50 rows in each detailed register
Choose what you want to understand
If this is your first Architecture Report, start with Architecture Overview for the big picture. Then choose the question you care about; each description explains what that chapter will help you understand. Each link opens the chapter in the full report.
-
01
Architecture OverviewStart here to see how the library is divided across modules and packages, how those parts depend on each other, and where its five dependency loops appear in the whole-project map.
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
- 02 Cycle EvidenceSee all five dependency loops together, then trace each one through the packages and relationships that keep it closed.
- 03 Hotspot RiskFind packages where changes may spread widely, then see whether the pressure comes from incoming dependencies, exposed code, or tightly connected internals.
- 04 Governance AuditSee the owner-approved boundary decision beside its reason and current dependency path, so you can judge whether the documented exception still matches the code.
- 05 Evidence AppendixUse the capped package-metric and dependency registers when a deeper review or handoff needs more literal evidence than the short diagnostic lists.
What this report covers
- Source revision
- 676954dfb8915e144b1737d1cc9bf968d0f874a7
- Licence
- Apache-2.0
- Language and evidence
- Java · compiled JVM bytecode from 10 production roots
- Governed boundary
- org.simplejavamail.email.internal → org.simplejavamail.mailer.internal
- Decision
- Intentional · package scope · active
- Report contents
- Whole project + Governance Audit + detailed evidence appendix
- Report date
- 31 July 2026
- AtlasArc version
- 1.0.0
How to use this case
Context here, evidence in the report
Use this page to understand the project snapshot and scope. Open the report to inspect the architecture chapters themselves.
View project sourceHow this example was prepared
-
Use the recorded source revision
Check out the Simple Java Mail revision linked on this page and build the ten production class roots with Maven 3.9.10 on JDK 21.
-
Choose the project evidence
Select the production class roots and retain the project scope across the represented modules.
-
Record the governed decision
Mark the package-scoped email.internal → mailer.internal boundary as Intentional with the project owner's recorded reason.
-
Choose the report chapters
Include the whole-project chapters, Governance Audit, and detailed evidence tables with a 50-row maximum.
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.