domain

Domain Docs

How the engineering skills should consume this repo's domain documentation when exploring the codebase.

This repo is single-context: one CONTEXT.md and one docs/adr/ at the root. (The multi-context layout — a root CONTEXT-MAP.md pointing at per-package CONTEXT.md files — does not apply here and has been left out; this is a single npm package with no workspaces.)

Before exploring, read these

• CONTEXT.md at the repo root
• docs/adr/ — read ADRs that touch the area you're about to work in

If either doesn't exist, proceed silently. Don't flag its absence; don't suggest creating it upfront. The /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture) creates them lazily when terms or decisions actually get resolved.

File structure

/
├── CONTEXT.md
├── docs/adr/
│   ├── 0001-....md
│   └── 0002-....md
└── src/

Use the glossary's vocabulary

When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.

If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for /domain-modeling).

The domain here is the Dataverse metadata model, whose vocabulary is fixed by Microsoft rather than by this project — attribute and column name the same thing, as do entity and table, and Local vs Global OptionSet is a real distinction with a specific meaning. CONTEXT.md is where those choices get pinned down.

Flag ADR conflicts

If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:

Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…