domain-modeling

Actively challenge, resolve, and record domain terms/decisions while designing. Merely reading CONTEXT.md is not domain modeling.

Files

Use root CONTEXT.md and docs/adr/ for one context. If root CONTEXT-MAP.md exists, follow it to context-local CONTEXT.md and ADRs; system-wide ADRs stay under root docs. Create files only when the first real term/decision exists.

During the session

Challenge the glossary

When user language conflicts with CONTEXT.md, quote the mismatch and ask which meaning wins.

Sharpen language

Replace vague/overloaded words with a proposed canonical term, distinguishing nearby concepts explicitly.

Test scenarios

Probe relationships and boundaries with concrete edge cases until terms are precise.