architecture-decisionslisted

# Architecture Decisions ## Overview Architecture Decision Records (ADRs) are lightweight documents that capture architectural decisions together with their context, alternatives considered, and consequences. They are the institutional memory of the architecture. **Purpose:** An ADR answers the question: "Why does the architecture look the way it does?" Future readers — including future you — should be able to understand any structural decision without needing to ask the original author. **Core rule:** One ADR per decision. A decision is a single, clear choice with trade-offs. --- ## ADR Template ### Blank Template ```markdown --- adr: {NNN} # int, matches filename title: {Short Title} status: Proposed # Proposed | Accepted | Rejected | Deprecated | Superseded chosen: {picked option} # one token/phrase — the option adopted decision: > # ONE sentence: the verdict in plain words {We will ... / We will not adopt ... because ...} supersedes: {ADR-MMM | null} date: {YYYY-MM-DD} ratified_by: null # "{human} {YYYY-MM-DD}" — set ONLY on Accept/Reject --- # ADR-{NNN}: {Short Title} **Status:** Proposed | Accepted | Rejected | Deprecated | Superseded by ADR-{NNN} **Date:** {YYYY-MM-DD} ## Context {Describe the situation and the forces that led to this decision. What problem were you solving? What constraints were in play? Why was a decision needed at all?} ## Decision {State the decision clearly and directl