Architecture Decision Records¶
ADRs are short, immutable records of decisions taken on the architecture of the platform. Each ADR has a number, a status, the context it was decided in, the decision itself, and the consequences — both good and bad.
We add an ADR when a decision will be hard to reverse, when it shapes how new contributors will read the codebase, or when it locks in a trade-off worth remembering. We do not write ADRs for routine implementation choices.
Index¶
| # | Title | Status | Date |
|---|---|---|---|
| 001 | Multi-framework rule book | Accepted | 2026-05-09 |
| 002 | Counsel routing deferred | Accepted | 2026-05-09 |
| 003 | Frameworks as products | Accepted | 2026-05-09 |
| 004 | SaaS first, single-tenant deployable | Accepted | 2026-05-09 |
| 005 | MkDocs Material | Accepted | 2026-05-09 |
| 006 | ntfy deploy notifications | Accepted | 2026-05-09 |
Statuses¶
- Accepted — the decision is in force; the codebase reflects it.
- Deprecated — the decision is no longer in force, but it remains here as historical context.
- Superseded by NNN — replaced by a later ADR; the link points at the successor.