# Domain Docs

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

## Before exploring, read these

- **`CONTEXT-MAP.md`** at the repo root — it points at one `CONTEXT.md` per app/context
- **`docs/adr/`** — read ADRs that touch the area you're about to work in
- **Context-specific `docs/adr/`** — also check `apps/<app>/docs/adr/` for context-scoped decisions

If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The producer skill (`/grill-with-docs`) creates them lazily when terms or decisions actually get resolved.

## File structure

This is a multi-context monorepo. The layout is:

```
/
├── CONTEXT-MAP.md                     ← index pointing to per-app contexts
├── docs/adr/                          ← system-wide decisions
│   ├── 0001-*.md
│   └── 0002-*.md
├── apps/
│   ├── da_product_app/
│   │   ├── CONTEXT.md                 ← domain concepts for this app
│   │   └── docs/adr/                  ← app-scoped decisions
│   ├── upi_core/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/
│   ├── upi_dynamic/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/
│   ├── upi_static/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/
│   └── upi_web/
│       ├── CONTEXT.md
│       └── docs/adr/
└── ...
```

## 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 the relevant `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 `/grill-with-docs`).

## 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…_