domain-modelinglisted

# Domain Modeling Actively build and sharpen the project's domain model as you design. This is the *active* discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `CONTEXT.md` for vocabulary is not this skill — that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.) Two files, two different contents: sharpened glossary terms go to `CONTEXT.md`; decisions that constrain architecture or behaviour go to the active scope ledger (`docs/scope/<slug>.md`) with a disposition tag. Don't conflate them — a term is not a decision, and a decision is not a definition. ## File structure Most repos have a single context (the `docs/adr/` trees below illustrate a repo with no existing decision record; resolve the ADR's home first, per [references/ADR-FORMAT.md](references/ADR-FORMAT.md)): ``` / ├── CONTEXT.md ├── docs/ │ └── adr/ │ ├── 0001-event-sourced-orders.md │ └── 0002-postgres-for-write-model.md └── src/ ``` If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives: ``` / ├── CONTEXT-MAP.md ├── docs/ │ └── adr/ ← system-wide decisions ├── src/ │ ├── ordering/ │ │ ├── CONTEXT.md │ │ └── docs/adr/ ← context-specific decisions │ └── billing/ │ ├── CONTEXT.md │ └── docs/adr/ ``` Create files l