ultra-domain-modelinglisted

# Keep one file that fixes what each domain word means This is how implementation reaches the earlier documents — not by better retrieval, but by needing less of it. `CONTEXT.md` is a compressor, not an index. What implementation lacks is rarely the content of the product specification; it is the vocabulary, so that trace anchors, variable names, function names, and test names all line up. It serves Goal 4, Cognitive Coherence. ## Before you start 1. Read `CONTEXT.md` at the repository root if it exists. Every skill reads it for vocabulary; this one is for the moments that *change* it. 2. Read the owner's current wording verbatim — their words are the raw material. 3. Check the code for the same concept: type names, table names, function names. ## Definition of done - Every term settled in this exchange is in the file, written the moment it was settled rather than batched at the end. - Each entry defines what the term *is* in one or two sentences, and lists the wordings that lost. - The file still holds vocabulary only, carrying no implementation detail. ## The file Create it at the repository root the first time a term is actually settled, not before. This is the whole format: ```markdown # {project name} {One or two sentences: what this context is and why it exists.} ## Language **Order**: {One or two sentences. Define what it is, not what it does.} _Avoid_: Purchase, Transaction ## Relationships - One **Issue tracker** holds many **Issue** ## Flagged a