---
status: PROPOSED
date: YYYY-MM-DD
authors: []
---

# NNNN. [Title — use imperative verb phrase, e.g. "Use PostgreSQL for persistence"]

## Context

[What is the problem or opportunity? What forces are at play — technical,
political, social, project-specific? Leave no room for ambiguity about why
this decision was needed.]

## Decision Drivers

- [Driver 1 — e.g., "Must support concurrent writes from multiple services"]
- [Driver 2 — e.g., "Team has no experience with technology X"]
- [Driver 3]

## Decision

[State the decision clearly in active voice: "We will use X because…"]

## Alternatives Considered

### [Alternative 1]

- **Pros:** [advantages]
- **Cons:** [disadvantages]
- **Rejected because:** [specific reason]

### [Alternative 2]

- **Pros:** [advantages]
- **Cons:** [disadvantages]
- **Rejected because:** [specific reason]

## Consequences

### Positive

- [What becomes easier or better]

### Negative

- [What becomes harder or worse]

### Neutral

- [Side effects that are neither clearly positive nor negative]

## Non-goals

[Optional. What is explicitly out of scope for this decision? Stating
non-goals prevents scope creep and tells agents what NOT to implement.]

## Reversibility

[Optional. How would this decision be undone if needed? What conditions
should trigger reconsideration?]

## References

[Optional. Links discovered during research, related ADRs, prior art,
or any external resources that informed this decision.]