Domain-document workflow

This is a single-context repository. Read root CONTEXT.md before introducing or renaming domain concepts. Reuse its preferred terms in code, tests, APIs, specifications, and operations documents; avoid terms explicitly marked there.

Update CONTEXT.md when a durable concept, invariant, relationship, or ownership boundary changes. Update the approved specification when observable product intent changes. Update technical-implementation.md when as-built behavior changes. Create an ADR for a durable, hard-to-reverse architecture choice; do not use an ADR as a substitute for current behavior documentation.

Completion requires every modified domain term to be consistent across its public contract, tests, and governing documentation, with any intentional compatibility alias stated explicitly.