# CONTEXT — glossary & domain model

> **Authoritative for meaning.** When code, prose, or a plan disagrees with a definition here,
> **this file wins** — the term means what CONTEXT.md says it means, and the disagreeing thing is
> the bug. This is the *grill-with-docs* convention: plans are stress-tested against the language
> defined here, and **this file is updated inline** as decisions crystallize (don't let it lag
> the code).
>
> Keep entries short and cross-linked. A term defined here is the canonical name — use it
> verbatim in code, docs, and commits. ADRs (`docs/adr/`) record *decisions*; this file records
> *meaning*.

## Glossary

> Replace these placeholder entries with your project's real terms. Format:
> **Term** — definition in one or two sentences. Cross-link related terms in `**bold**`.

**`<Term A>`** — `<one-sentence definition of what it is and why it exists>`. Relates to
**`<Term B>`**. `<Note any constraint or invariant that is part of the term's meaning.>`

**`<Term B>`** — `<definition>`. Distinct from **`<Term A>`** in that `<the boundary between
them>`.