Diagram Index¶
One sentence: every diagram in the documentation, as diagram-as-code (Mermaid), with the page that explains it.
Sources live in docs/diagrams/ as .mmd files (render with any Mermaid tool: npx -y @mermaid-js/mermaid-cli -i <file>.mmd -o <file>.svg, mermaid.live, or your IDE). The same diagrams are embedded inline in their explanation pages, and the docs site renders them natively. The layered system diagrams derive from architecture-map.json โ update the JSON first, diagrams second. The database ERD is maintained inline in database-schema.md.
Interactive alternative¶
The architecture explorer renders the full system map interactively (3D layers, flow toggles, click-to-inspect), driven by architecture-map.json. It degrades to a 2D canvas without WebGL, and these static diagrams remain the accessible fallback.
Conventions¶
- Diagram-as-code first; no binary-only diagrams.
*suffix inside a diagram = planned/not implemented component.- Every diagram carries a
%%header comment naming its explanation page. - Adding a diagram: put the
.mmdhere, embed it in the owning doc, add a row to this table (validated byscripts/validate-docs.mjs).