Domain Modeling

Actively build and sharpen the project's domain model as you design. This is the active discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely reading GLOSSARY.md for vocabulary is not this skill; that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

File structure

/
├── GLOSSARY.md
├── docs/
│   └── decisions/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

Create files lazily, only when you have something to write. If no GLOSSARY.md exists, create one when the first term is resolved. If no docs/decisions/ exists, create it when the first decision record is needed.

During the session