# NNNN. Title in the imperative, naming the decision

- **Status:** Proposed | Accepted | Deprecated | Superseded by [NNNN](NNNN-slug.md)
- **Area:** Architecture | Chain | Crypto | Net | SPV | Storage | Wallet | UI | Testing | Distribution | Scope | Process
- **Recorded:** YYYY-MM-DD

## Context

The forces at play: the problem, the constraints, what was tried or rejected.
Facts only; link to code, issues or specs instead of restating them.

## Decision

What we do, in the active voice ("We use…"). Specific enough that a reviewer
can check the code against it.

## Consequences

What becomes easier, what becomes harder, new risks, follow-up work.
Be honest about the downsides.

## References

- `path/to/code.cs`
- Related ADRs, specs (BIPs), issues