# Architecture Decision Record

Use this template to capture architecture decisions during consulting sessions. Fill in each section as the decision is made. Save the result to the team's ADR directory.

```markdown
# ADR-[NUMBER]: [Title]

## Status
[Proposed | Accepted | Deprecated | Superseded]

## Context
What's the problem we're solving? What constraints, assumptions, and forces are at play?

* Business driver:
* Technical context:
* Constraints (budget, timeline, team capability, compliance):
* Key stakeholders:

## Options Considered

### Option A: [Name]
* How it works:
* Pros:
* Cons:
* Migration cost:
* Operational complexity:

### Option B: [Name]
* How it works:
* Pros:
* Cons:
* Migration cost:
* Operational complexity:

*(Add more options as needed)*

## Decision
**Chosen option:** [A / B / C]

**Rationale:**
1. [Primary reason]
2. [Secondary reason]
3. [Tiebreaker]

**Consequences:**
* Positive:
* Negative / tradeoffs accepted:
* What we're explicitly not doing:

## Verification
How will we know this was the right decision?

* [Metric or milestone]
* [Review date]

## References
* [Link to relevant reference file in this skill]
* [Link to vendor docs, case studies, or external sources]
```

## Usage

When I recommend a specific architecture or tool during a consulting session, I'll offer to produce an ADR. If you want one, say "capture that as an ADR" and I'll fill in the template from our conversation.