Architecture Decision Records¶
The permanent memory of engineering decisions. If a decision changed how we build systems and it is not here, it does not exist.
New here? The concepts — what an ADR is and why it works this way — are explained on the homepage. This page is the rulebook.
Rules¶
- One decision per file:
ADR-NNNN-kebab-title.md, numbered sequentially — copytemplates/adr.mdand fill every section (write "None." rather than deleting one). - ADRs are immutable once accepted — new context means a new ADR that supersedes
the old one (both keep their files; the old one changes only its
status). - Significant decisions arrive via RFC; urgent or small-but-worth- remembering decisions may be recorded directly, within 5 working days.
- Approval: 2 approvals on the PR. Approval means "the record is faithful and complete", not "I would have decided the same".
- Implementation PRs in delivery repos cite the ADR ID.
Lifecycle¶
proposed → accepted | rejected; later deprecated (no longer relevant) or
superseded (replaced — link the successor).
Index¶
No ADRs yet — the next decision we make starts this index.
| ID | Title | Status |
|---|---|---|