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 cover the host daemon, the firmware, and the graphics tooling alike.

Visual, protocol, and layout rationale is not in a document — it sits in Thai comments beside the code it governs, at the density the surrounding file already uses. Read the code you are about to change; the reasons are there.

Before exploring, read these

• CONTEXT.md at the repo root.
• docs/adr/ — read ADRs that touch the area you're about to work in.
• docs/hardware.md — only when you need a value measured off the real board.

If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them 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
├── host/
├── firmware/
└── tools/

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).

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…