Architecture decision record template
- Status: Proposed | Accepted | Superseded | Rejected
- Decision ID: TBD-xxx
- Date: YYYY-MM-DD
- Owners:
- Related issues:
- Supersedes:
Context
Section titled “Context”What product/technical problem requires a decision? Which non-negotiable HUE vision constraints apply?
Decision question
Section titled “Decision question”State one answerable question.
Constraints and decision criteria
Section titled “Constraints and decision criteria”- Product behavior
- Security/privacy
- Durability/recovery
- Portability/provider independence
- User experience
- Implementation and maintenance cost
- Migration/reversibility
Options considered
Section titled “Options considered”Option A
Section titled “Option A”Description, evidence, benefits, costs and risks.
Option B
Section titled “Option B”Description, evidence, benefits, costs and risks.
Experiments/evidence
Section titled “Experiments/evidence”Link disposable spikes, benchmarks, prototypes or source analysis. A plausible opinion is not evidence.
Decision
Section titled “Decision”The accepted option and why it best meets the criteria.
Consequences
Section titled “Consequences”Positive
Section titled “Positive”Negative/trade-offs
Section titled “Negative/trade-offs”Risks and mitigations
Section titled “Risks and mitigations”Implementation contract
Section titled “Implementation contract”What interfaces/behavior become fixed? What remains deliberately open?
Migration and rollback
Section titled “Migration and rollback”How can the decision be changed later? What data/API migration would be required?
Revisit triggers
Section titled “Revisit triggers”Concrete evidence or product change that should reopen this ADR.
Documentation/status updates
Section titled “Documentation/status updates”List TBI/TBD sections and issues affected by acceptance.