Showcases · Four pinned projects
Architecture evidence you can open
Four Architecture Reports from real open-source projects. Choose the architecture question that matters to you, read the project context, then open any chapter of the full report.
Four projects. Four distinct proof jobs.
This is not a ranking. Each project was selected to make a different report capability inspectable: breadth at scale, governed decisions, compiled Kotlin/JVM evidence, and project-generated TypeScript dependency data.
-
Full-depth report · Large modular Java
Spring Boot
Spring Boot supplies the large modular Java example: 1,026 report packages, focused boundary chapters, and a four-package dependency loop that closes through nested packages.
- Report packages
- 1,026
- Edges
- 1,114
- Cycle groups
- 1
- Chapters
- 8
-
Governance audit · Owner-approved decision
Simple Java Mail
Simple Java Mail supplies the governance example: Governance Audit places an owner-approved Intentional package-boundary decision, its reason, and current dependency evidence side by side.
- Report packages
- 52
- Edges
- 220
- Cycle groups
- 5
- Chapters
- 5
-
Kotlin project · Cycle evidence
Detekt
Detekt supplies the Kotlin/JVM example: nine cycle groups and hotspot evidence from 32 production roots and 2,328 compiled classes.
- Report packages
- 67
- Edges
- 198
- Cycle groups
- 9
- Chapters
- 4
-
TypeScript project · Generated dependency data
Vue Core
Vue Core supplies the TypeScript example: project-generated Dependency Cruiser data becomes an Architecture Report over source folders rather than JVM packages.
- Source folders
- 31
- Edges
- 94
- Cycle groups
- 8
- Chapters
- 4
Context first. Report second.
-
01
Read the case file
See what was built, what AtlasArc analyzed, why this report composition was chosen, and which limitations apply.
-
02
Open the report index
Browse the report by chapter. It opens separately from the case notes so the architecture evidence has room to breathe.
-
03
Print the continuous record
Use Printable Version when you want one review packet or a PDF rather than the linked chapter view.
The stable output contract
Know what the report preserves
The documentation explains report choices, analysis state, chapter composition, standalone browsing, and Printable Version before you evaluate the examples.