# Explanation: <Topic — the concept, not the task>

<!-- GENRE: Explanation (understanding-oriented)
     Goal: build a mental model — the WHY, the history, the trade-offs.
     Voice: discursive, reflective; use analogies where helpful.
     Rule: do not give step-by-step instructions here; link to how-to guides instead.
           Do not invent examples that imply a specific stack choice. -->

## Background

<!-- What problem does this concept address?
     Where did it come from, and why does it matter in this project?
     Keep to 2–4 short paragraphs; avoid bullet lists here — prose reads better. -->

## Core idea

<!-- The central mental model in 1–3 paragraphs.
     Use an analogy if the concept is non-obvious.
     Aim for the clearest accurate description, not the most exhaustive one. -->

## Key design decisions and trade-offs

<!-- Each meaningful decision this concept embodies gets a sub-heading or bold label.
     For each: state the decision, the alternative(s) considered, and why this one
     was chosen. Link to the relevant ADR for governance-level decisions. -->

**Decision: <label>**
Reasoning and trade-offs.

**Decision: <label>**
Reasoning and trade-offs.

## What this does NOT cover

<!-- Set the scope boundary explicitly.
     Name the adjacent concepts this explanation deliberately excludes,
     and link to the explanation or reference page that covers them. -->

## Further reading

<!-- Links to the reference page for the precise API, the how-to guides for common
     tasks, and any ADRs or external sources that influenced this design. -->