ADR-NNNN: Decision title¶

• Status: Proposed | Accepted | Superseded | Rejected.
• Recorded: YYYY-MM-DD.
• Decision authority/date: exact owner/review/contract reference, or unknown.
• Implementation: current | partial | planned | private/gated. Include scope.
• Supersedes: linked ADR, if any. Add a reciprocal link after acceptance.

Context¶

What concrete problem requires a durable decision? Which constraints already apply? Do not introduce a new requirement as if it had already been approved.

Decision¶

State one coherent choice, scope, invariants and explicit non-goals. Separate acceptance of the choice from implementation, dataset/access permission and public activation. Identify any existing gates that still apply.

Alternatives and consequences¶

Name realistic alternatives and tradeoffs. Mark reconstructed comparisons as analysis rather than historical deliberation. Include costs and limitations, not only advantages. Do not reopen settled questions without a trigger.

Evidence¶

Link authoritative owner decisions/specs/contracts, code/test anchors where useful and exact acceptance evidence. Test existence is not a passing test run. Do not invent approval dates, reviewers, measurements or completion claims.

Revisit when¶

Give concrete conditions that justify reconsidering the decision. A changed meaning requires a successor ADR and applicable approvals/specifications/tests; editorial corrections do not.