architecture-decision-record

# Architecture Decision Record ## Step 1: Understand the decision Ask the user: > What architecture decision do you need to document? Please share: > - **Decision title** (e.g., "Use Aurora Serverless v2 for the orders database") > - **Context** — What problem are you solving? What constraints exist? > - **Options considered** (at least 2) — or ask me to suggest alternatives If the user has already described the decision, proceed directly. ## Step 2: Evaluate options against WA pillars For each option, assess impact on all six pillars: | Pillar | Option A | Option B | Option C | |--------|----------|----------|----------| | Operational Excellence | | | | | Security | | | | | Reliability | | | | | Performance Efficiency | | | | | Cost Optimization | | | | | Sustainability | | | | Use: ✅ Positive | ➖ Neutral | ⚠️ Trade-off | ❌ Negative ## Step 3: Identify trade-offs For the recommended option, explicitly state: - What you gain - What you give up - Under what conditions the decision should be revisited ## Step 4: Produce the ADR Output using the standard ADR format: ```markdown # ADR-{number}: {Decision Title} ## Status {Proposed | Accepted | Deprecated | Superseded by ADR-X} ## Date {YYYY-MM-DD} ## Context {What is the problem? What forces are at play? What constraints exist?} ## Decision {What is the change that we're proposing and/or doing?} ## Options Considered ### Option 1: {name} - **Description**: {how it works} - **Pros**: {benefits} - **Cons**: {draw...