# NNNN. <Short title that describes the decision>

**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded
**Deciders:** @handle-1, @handle-2
**Supersedes:** —
**Superseded by:** —

## Context

What forces are at play? What problem are we trying to solve? Include
anything a future reader needs to understand why this decision mattered
at the time — team size, scale assumptions, tech constraints, deadlines.
2–4 sentences.

## Decision

The choice, in one sentence: "We will use X."

Then a short paragraph on how we'll use it.

## Alternatives considered

- **Y** — rejected because <one-line reason>
- **Z** — rejected because <one-line reason>

## Consequences

### Positive
- What this unlocks.
- What it makes easier.

### Negative
- What trade-off we're accepting.
- What we'll have to revisit later.

### Neutral
- What this doesn't change.

## Links

- PR: #N
- Related ADR: [NNNN. Title](NNNN-slug.md)
- Original discussion: <chat link, Slack link, or design doc URL>

<!--
Template source: https://whychose.com/seo/adr-template-markdown
Nygard 2011 original: https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions
Keep it under 250 words. Long ADRs don't get read.
-->