# NNNN. Title — short imperative

- **Status:** Proposed | Accepted | Superseded by NNNN | Deprecated
- **Date:** YYYY-MM-DD
- **Deciders:** @handle1, @handle2
- **Related:** ADR-NNNN, runbook/spec/PR links

## Context

What's true today + what problem this decision addresses. Include forces — non-negotiables, constraints, costs, deadlines. 1–3 paragraphs.

## Decision

What we will do. One sentence if possible; expand only if the implementation has load-bearing detail.

## Alternatives considered

| Option | Why rejected |
| --- | --- |
| A — … | … |
| B — … | … |

Be honest. "We didn't have time to learn X" is a valid reason — record it.

## Consequences

### Positive

- …

### Negative

- …

### Neutral (worth knowing)

- …

## Compliance

How the decision interacts with PDPA / GDPR / SOC2 / accessibility / our SLOs. Often nothing — that's a valid answer.

## References

- Links to RFCs, blog posts, prior art.
- The PR that implemented it (added after merge).

---

## How to use this template

1. Copy this file: `cp docs/decisions/0000-template.md docs/decisions/NNNN-<kebab-title>.md`.
2. Find the next number: highest in `docs/decisions/` + 1.
3. Fill every section. If a section is N/A, say so explicitly — don't delete it.
4. PR + reviewers from the relevant teams.
5. On merge, status becomes **Accepted**.
6. If a future ADR replaces this one, update Status to `Superseded by NNNN` (and the new ADR points back).
