# ADR [number]: [one decision in a short title]

Keep one decision per file. Replace the bracketed prompts with what is actually known; mark unknowns rather than inventing evidence. Save the record alongside the code, for example as docs/decisions/0001-short-title.md.

## Decision

We will [specific action and scope].

## Context

Date of the decision: [YYYY-MM-DD]
Decision owner and reviewers: [people responsible for the choice]

[Describe the constraint, workload, existing system and deadline that matter now. Separate measured facts, assumptions and unknowns. Link to the issue, design discussion or reproducible evidence.]

## Alternatives rejected

- [Alternative A]: [Why it does not satisfy the relevant constraints; what it would do better.]
- [Alternative B or the current approach]: [Why it was not chosen; when it would become preferable.]

## Consequences accepted

[State the useful effect and the cost we deliberately accept. Name the changed failure mode, operational responsibility, dependency or reversal cost. Describe what observation would justify revisiting the choice.]

## Status

Proposed | Accepted | Superseded — choose one.

Supersedes: [previous record, when applicable]
Superseded by: [replacement record, when applicable]

When the decision changes, create a new record. Mark this record as superseded and link to the replacement; do not rewrite its historical context to match the new system.

---

This template follows the five-field structure in Software Made Clear's architecture decision records guide: https://softwaremadeclear.com/architecture-decision-records/
It is a blank working template, not a claim that any decision has already been reviewed or approved.