silo-domain-modelinglisted

# Domain Modeling Actively build and sharpen Silo's domain model as you design — not just read it. Challenging terms, inventing edge-case scenarios, and writing the glossary/decisions down the moment they crystallize is the active half of this skill; merely reading the docs below for vocabulary is a one-line habit any skill can do. ## Where things live - **`docs/domain-language.md`** — the glossary. Ubiquitous language for the product: Workspaces, Navigator, Panels & Docking, Agents, Worktrees, Keybindings, and any other cluster of terms specific to Silo. Single file, single context — Silo doesn't split into bounded contexts, so there's no `CONTEXT-MAP.md`-style index to maintain. - **`docs/decisions/`** (ADRs) — decisions already **made**. Read `docs/decisions/README.md` first for the ADR-vs-RFC test, numbering, and status vocabulary, and use `docs/decisions/template.md` for the format. Update the index table in `README.md` when adding one. - **`docs/proposals/`** (RFCs) — forward-looking designs **not yet decided**. Read `docs/proposals/README.md` and use `docs/proposals/template.md`. Same index-update rule. ## During the session ### Challenge against the glossary When a term conflicts with `docs/domain-language.md`, call it out immediately. "The glossary defines 'cancellation' as X, but you seem to mean Y — which is it?" ### Sharpen fuzzy language Propose a precise canonical term for vague or overloaded language. "You're saying 'active' — the Navi