Architecture
What the system optimises for, and the shape that is in the tree.
Optimisation order, adopted with the engineering rules (decision 35): security and privacy, then evolvability for AI authors, then operational simplicity on one host. Horizontal scale, multi-region availability and zero-downtime for every change are out of scope until a closed test shows a need (ADR 0011). The checked rule table stays in docs/human/architecture.md.
One Compose stack on one host. A request enters one process under interfaces/, which calls a product rule under domains/ and reaches Postgres, the PDS and the public network only through infrastructure/. The UI in the tree is apps/web. The interfaces in the tree are interfaces/web (the SvelteKit web server), interfaces/indexer and interfaces/pds-admin. Decision 34 (docs/ai/PLAN.md): a folder appears when its first code lands. Roadmap: docs/ai/PLAN.md.
| Page | Covers |
|---|---|
| Processes | Containers, database roles, networks |
| Layers | Folders and the import allowlist |
| Data flow | One account-page request; Postgres and the PDS |
| Trust boundaries | Edge, one process per container, egress, trusted base |
| Security model | What each check is for |
| Decisions | ADR index |