# ADR-NNNN: {{brief decision title}}

- **Date:** YYYY-MM-DD
- **Status:** Proposed | Accepted | Superseded by ADR-XXXX | Deprecated
- **Owners:** {{who decided}}

## Context

What we observed, what problem existed, what constraints applied. Link to specific snapshots from `insights/` (e.g. `insights/analytics/2026-03-27.md`), commits, tickets — so that six months from now we can reconstruct why this was discussed at all.

## Decision

What exactly we decided to do. One or two short sentences. No caveats, no alternatives here — alternatives go below.

## Alternatives considered

- **Option A** — what it is, why we rejected it
- **Option B** — what it is, why we rejected it

## Consequences

- **Positive:** what will improve / become simpler
- **Negative / risks:** what will become more complex, what might break, what will need maintenance
- **What needs to change in other layers:** updates to `product/`, `spec/`, `design/`, migrations, etc.

## How we'll verify the decision worked

A specific metric and threshold + deadline. E.g. `checkout_completed > 0 within 7 days of deploy`. Without this, the decision can neither be confirmed nor rolled back.
