domain

# Domain — ubiquitous language Make the caller's domain language precise enough to use consistently in acceptance examples, code and conversation. A bounded context is the area in which a term has one agreed meaning and an owner for its rules. Different contexts may legitimately use the same word differently. ## Procedure 1. Locate the caller repository's existing vocabulary owner from its instructions, domain docs or contracts. Read only the terms and context boundaries relevant to the task. Cite the source when returning a definition; a lookup is read-only. If no definition exists, distinguish an observed code name from a proposed term. 2. For an ambiguous term, identify the actor, state, operation and observable result it denotes. Compare the intended meaning with relevant callers, types and tests. Report a disagreement between code and accepted intent explicitly; neither silently rewriting intent to match code nor renaming a bug fixes it. 3. Use a concrete example to distinguish competing meanings. For branching behavior, express the consequential boundary as Given/When/Then. Reuse the accepted example in implementation and validation. Ask only when an unresolved distinction would change behavior or ownership; do not interview for a lookup. 4. Use the settled term in scenario names, operations, types and documentation. When a word crosses contexts, name each meaning and the translation between them instead of imposing one global definit...