Developer documentation

Read top to bottom for onboarding; skip ahead only when you already know the layers.

Principles

We document systems, not every type in the repo. Each architecture page follows the same spine:

1. Purpose — what problem it solves.
2. Code location — where to open in the tree.
3. Main interfaces / classes — contracts you actually implement or inject.
4. Startup / registration — how it wires into DI and bootstrap.
5. How to extend — concrete steps.
6. Gotchas — ways contributors break things.

Reading order

Step	Doc
1	Setup
2	Architecture overview
3	Layer docs: Core, Infrastructure, UI
4	Startup flow
5	Dependency injection
6	Module system
7	Data storage, AI and RAG pipeline
8	Contributing, Coding standards, Testing, Release process

Users

End-user docs live under Students (student docs home).