# ADR-NNNN: <Decision title>

- **Status:** Proposed | Accepted | Superseded by ADR-XXXX | Deprecated
- **Date:** YYYY-MM-DD
- **Deciders:** <names or roles>
- **Tags:** <area-tags>

## Context

State the problem in your own words. What forces are in play? What constraints, requirements, or observations drove this decision? Avoid jumping to the answer.

## Decision

State the decision in one paragraph. Be precise. The decision should be implementable from this paragraph alone.

## Consequences

### Positive

- What this enables or simplifies.

### Negative

- What this costs or constrains.

### Risks

- What could go wrong, and what are the mitigations.

## Alternatives considered

For each: a short description, why it was attractive, and why it was rejected. Empty list is a smell — every real decision has alternatives.

### Alternative A: <name>

- Description.
- Why it was attractive.
- Why it was rejected.

## Validation against the four principles

1. **First principles.** Why this construct exists.
2. **Modular.** What can replace this without rewriting the rest.
3. **Extensible.** How new variants are added later.
4. **Config-driven.** Which behaviors are exposed via `ConfigKey`.

## References

- Related ADRs.
- Related issues / PRs.
- External links.
