Architecture
The why behind the design. Each page is the readable companion to a specific architectural decision; together they explain the trades that shape the system.
| Page | What it argues |
|---|---|
| Why a thin centre | The control-plane decision in plain prose. |
| Three concentric rings | The topology: control plane between fleets and consumers. |
| Why no central database | Why we explicitly rejected Postgres as source-of-truth. |
| Why API-first | Why writes use the GitHub Contents API, not local-clone-and-push. |
| Trade-offs accepted | The full enumeration of what we gave up. |
See also
Section titled “See also”- Control-plane decision — the formal record these pages annotate.
- Concepts — the mental-model layer above architecture.
- Meta-rules — the invariants the architecture exists to uphold.