Showcases · Four pinned projects

Architecture evidence you can open

Four unchanged HTML Architecture Reports, generated from real open-source builds with the same pinned AtlasArc 1.0.1 generator. Choose the architecture question that matters to you, inspect its basis, then open every chapter.

Evidence register

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, Kotlin/JVM evidence, and TypeScript artifact-backed analysis.

  1. Full-depth report · Large modular Java

    Spring Boot

    The report spans 261 stable production class roots and 8,030 compiled classes, with all seven chapters selected and the large-project Matrix and Composition guards left visible.

    Report packages
    1,026
    Edges
    1,114
    Cycle groups
    1
    Chapters
    7
    Read the case file Open generated report
  2. Governance audit · Owner-approved decision

    Simple Java Mail

    The governance case. The four-chapter report keeps the accepted cycle boundary, its recorded reason, and its current structural evidence together in Governance Audit.

    Report packages
    52
    Edges
    220
    Cycle groups
    5
    Chapters
    4
    Read the case file Open generated report
  3. Kotlin-heavy · JVM evidence

    Detekt

    The Kotlin/JVM case. Detekt exercises the same compiled-evidence path over 32 production roots and 2,328 classes, with cycle and hotspot chapters generated from a pinned full build.

    Report packages
    67
    Edges
    198
    Cycle groups
    9
    Chapters
    3
    Read the case file Open generated report
  4. TypeScript · Artifact-backed analysis

    Vue Core

    The artifact-backed case. A Dependency Cruiser graph over 12 production source roots proves the same report product can consume TypeScript evidence without pretending it came from bytecode.

    Source folders
    31
    Edges
    94
    Cycle groups
    8
    Chapters
    3
    Read the case file Open generated report
Reading route

Context first. Generated evidence second.

  1. 01

    Read the case file

    See what was built, what AtlasArc analyzed, why this report composition was chosen, and which limitations apply.

  2. 02

    Open the report index

    Browse the unchanged standalone output by chapter. It uses no website chrome and loads only after you choose it.

  3. 03

    Print the continuous record

    Use Printable Version when you want one review packet or a PDF rather than the linked chapter view.

Shared provenance

Generator-pinned, no hand-edited output

Each public folder records its AtlasArc generator build in the surrounding case file. The standalone HTML is published byte-for-byte; project framing, source attribution, reproduction steps, timings, hashes, and caveats live outside the generated output.

Generated
31 July 2026
Report files
25 HTML files
Public curation
None inside generated output
Affiliation
Examples do not imply project endorsement

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.

Read Reports and exports Java · Kotlin · TypeScript