loom-domain-language-and-decisionslisted

# loom-domain-language-and-decisions Domain language and decisions is a shaping playbook. It challenges a proposed change against the project's current vocabulary, behavior, and decisions, then routes resolved language to knowledge and durable tradeoffs to constitution decisions. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-knowledge`, `loom-constitution`, `loom-research`, `loom-specs`, `loom-plans`, `loom-tickets`, and `loom-evidence`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. It does not create a separate glossary or decision-record surface. Loom records carry the durable results. ## Use This Playbook When Use this playbook when: - a plan or spec uses vague, overloaded, or conflicting terminology - a domain concept needs a canonical name before implementation - code and operator language appear to disagree - an architecture choice may deserve durable precedent - a feature spans domain boundaries or context ownership - a future agent would likely misunderstand the work without shared language Skip it for generic implementation terms that do not help future agents understand this project. ## Route Use this route: ```text load language -> challenge terms -> test scenarios -> resolve -> record -> route ``` ## Load Language Before asking the operator questions, inspect existing Loom records and nearby source context. Read what is r