<!--
  Architecture Decision Record template, from Blueprint Catalog (https://catalog.mikereams.com/library?s=templates).
  CC BY 4.0, Mike Reams. Copy it, rename it, change it to fit your practice.
  One decision per record. Write it when the decision is made; do not edit it afterward. A later change of mind is a
  new record that supersedes this one.
-->

# ADR-NNNN: <the decision, as a short statement>

| Field | Value |
|---|---|
| Status | Proposed · Accepted · Superseded by ADR-NNNN · Withdrawn |
| Date | YYYY-MM-DD |
| Deciders | <names or roles who own the decision> |
| Consulted | <who gave input> |
| Scope | <system, domain or capability this applies to, e.g. BC-… or a product name> |

## Context

What forces are at play: the problem, the constraints (time, cost, skills, regulation), the quality attributes that
matter most here, and anything already decided that this depends on. Facts, not the answer.

## Options considered

1. **<Option A>** — one or two lines on what it is.
2. **<Option B>** — …
3. **Do nothing** — include it when it is a real option.

## Decision

We will <chosen option>, because <the one or two reasons that tipped it>.

## Consequences

- **Gains:** what gets easier or better.
- **Costs:** what gets harder, what we now have to run or pay for, what we give up.
- **Risks and follow-ups:** what could prove this wrong, and what we will watch (a metric, a date, a fitness function).

## Links

- Related records: ADR-…
- Evidence: benchmarks, spikes, vendor documents, tickets.
