Academy
The academy is the reader-orientation layer of the whitepaper. It explains how to approach the repository, how the teaching modules map onto the codebase, and what validation discipline should remain in view while you read.
What this section does
- turns the repository from a list of folders into a legible curriculum
- names the evidence standards before you encounter benchmark numbers or concurrency claims
- keeps the original learning path reachable without letting it overshadow the architectural story
Reading modes
| Reader posture | Start here | Why |
|---|---|---|
| evaluator checking technical depth | Module Atlas | It links each topic to concrete code, tests, and benchmarks. |
| maintainer checking rigor | Validation Doctrine | It defines the evidence ladder used across docs and code review. |
| practitioner trying to get productive quickly | Quick Start | It gets you to a verified local build before you branch into deeper study. |
| reader following the original topic sequence | Learning Path | It preserves the pedagogical order of the example modules. |
Core academy pages
| Page | Main question answered | Outcome |
|---|---|---|
| Module Atlas | Which repository surface teaches which concept? | A map from modules to code, tests, and benchmarks. |
| Validation Doctrine | What counts as trustworthy evidence here? | A preset-first rubric for correctness and performance claims. |
| Learning Path | In what order should I study the examples? | A topic sequence that remains close to the runnable code. |
Recommended sequence
- Read the landing page for the repository thesis and validation claims.
- Use the Module Atlas to choose a module or subsystem.
- Read the Validation Doctrine before trusting benchmark numbers or concurrency claims.
- Move into Architecture when you need repository-level context.
- Drop into the Playbook when you want commands, not commentary.
Relationship to the rest of the site
The academy deliberately stops short of being a beginner course. It is an orientation layer for expert readers who want fast answers to three questions:
- Where is the code that matters?
- How is it validated?
- Which page should I read next to confirm or challenge a claim?
If you already know the project well, you may only need the reference and research sections. For everyone else, the academy is the shortest route to a disciplined first read.