ADR NNNN: Title in the imperative or as a statement¶
- Status: Proposed | Accepted | Superseded by ADR NNNN (link it) | Deprecated
- Date: YYYY-MM-DD
Context¶
The forces at play: the problem, the constraints, and what PLAN.md says about it. Link the relevant PLAN.md section with an anchor, e.g. §2.1.
Decision¶
What we do, stated so that a reviewer can check code against it. Cite the contract artifacts
that encode it (e.g. schemas/intent/v1.json).
Consequences¶
Positive¶
- What becomes easier or safer.
Negative¶
- What becomes harder, slower or more expensive; what we give up.
Open questions¶
- What PLAN.md marks as unverified (⚠️) or open, and what this decision leaves to a later story.
Alternatives considered¶
- Alternative. Why it was not chosen.
References¶
- PLAN.md sections, as relative links with anchors, e.g. PLAN.md §2.1
- Contract files, issues, external sources.