# ADR-NNNN: Short decision title

| Field | Value |
|-------|-------|
| Status | Proposed / Accepted / Deprecated / Superseded by [ADR-XXXX](adr-XXXX.md) |
| Date | YYYY-MM-DD |
| Deciders | @name, @name |
| Tags | architecture, storage, api |

## Context

What is the issue we are deciding? Describe the forces at play:
technical constraints, business requirements, deadlines. Include enough
context that a newcomer can understand the problem without asking.

## Decision

What is the change we are making? State it in one clear, active sentence.
Use "We will..." not "We should..." or "We could...".

## Alternatives considered

### Option A – name

- Pros: ...
- Cons: ...
- Why rejected: ...

### Option B – name

- Pros: ...
- Cons: ...
- Why rejected: ...

## Consequences

### Positive

- What gets better because of this decision

### Negative / risks

- What gets harder, what we accept as cost

### Follow-ups

- [ ] Action item one
- [ ] Action item two

## References

- [Related discussion](https://example.com)
- [Prior art](https://example.com)