Domain Modeling

Build and sharpen the project's domain model as you design: challenge terms, invent edge-case scenarios, and write terms and decisions down the moment they crystallize.

File structure

For a vocabulary lookup, apply only this section and read the selected existing files as context. Continue with the active modeling sections only when the task calls for changing terms or recording decisions.

Read docs/agents/domain.md when present and use its recorded glossary, map, and ADR paths. Without recorded paths, use GLOSSARY-MAP.md or the root GLOSSARY.md; existing CONTEXT-MAP.md and CONTEXT.md remain valid. References to GLOSSARY.md throughout this skill mean the selected glossary, including a configured or legacy path.

The default layouts for new and migrated repositories:

• Single context (most repos): a root GLOSSARY.md, with ADRs in docs/adr/.
• Multiple contexts: a root GLOSSARY-MAP.md points to each context's directory (such as src/ordering/), which holds that context's GLOSSARY.md and a docs/adr/ for context-specific decisions. The root docs/adr/ holds system-wide decisions.

Follow a map to the context the work relates to. When the match is unclear, a vocabulary lookup reads each plausible context's glossary; active modeling asks the user.

During the session