12.6 ADRs and decisions
Architecture decision records in platform-spec—one file per choice, ADRs tab in the reader.
ADRs and decisions
Long meetings deserve short records. ADRs capture closed platform choices so the spec reader’s ADRs tab is the argument archive—not Slack scrollback.
Where they live
Section titled “Where they live”platform-spec/<domain>/<area>/<feature>/adr/<slug>.mdxInception decisions: Project inception.
File contract
Section titled “File contract”Each ADR must include:
| Field / section | Purpose |
|---|---|
specLevel: adr | Reader routing |
adrId | Stable id (e.g. D-CORE-CONC-0003) |
adrStatus | Accepted / Superseded / Proposed |
## Context / ## Decision / ## Consequences | Actual content |
Hub ## Decisions tables index adrId entries—avoid duplicating full prose only in index.mdx (Spec authority).
Example topics you will see
Section titled “Example topics you will see”Superseded
Section titled “Superseded”When a decision dies, mark adrStatus: Superseded and point to the replacement adrId—Git revision notes, not hidden URL versions.