This directory contains Architecture Decision Records (ADRs) for the DLM-proposer + AR-verifier project. Each ADR captures a single architectural decision, the context that led to it, the alternatives considered, and the consequences of choosing one path over another.
Code shows what we built. ADRs show why — and just as importantly, what we deliberately rejected and on what grounds. Without ADRs, every new contributor (human or agent) re-derives the same decision tree from scratch and either burns time or re-opens settled debates.
We follow a lightweight variant of the Michael Nygard format: Context → Decision → Consequences, plus an explicit Alternatives considered section because most of the value comes from showing the reader what was not chosen.
- File name:
NNNN-kebab-case-title.mdwhereNNNNis a four-digit zero-padded monotonically increasing number. - Status:
Proposed/Accepted/Superseded by NNNN/Deprecated. - Once
Accepted, an ADR is immutable except for theStatusfield. Disagreements are resolved by writing a new ADR that supersedes it. - Length: aim for ≤ 5 pages of rendered markdown. If longer, split.
Note: ADR numbering is monotonically increasing; in-flight or planned numbers (0005) appear in the index so readers can see the planned shape of the decision tree even before those ADRs are written. When an ADR moves from "Planned" to "In flight" it gets a PR link; when it merges, the row updates to "Accepted" with a file link.