# Agent Domain Docs

Zonegaze Matrix uses a project-memory model rather than a single root `CONTEXT.md`.

## Read Order

1. `AGENTS.md`
2. `zonegaze/memory/README.md`
3. `zonegaze/memory/project-map.md`
4. Relevant `zonegaze/memory/agent-operating-model/*.md`
5. Relevant active tracker under `zonegaze/memory/<feature>/`
6. `zonegaze/memory/project-understanding.md` only for broad architecture/product-boundary questions
7. `docs/adr/` when a hard-to-reverse architecture decision may already exist

## Domain Modeling

- Use `domain-modeling` when a term, product concept, module name, or architectural decision is ambiguous or recurring.
- Keep glossary-like facts compact and close to the owning project-memory file.
- Use `docs/adr/` for hard-to-reverse, surprising, trade-off-heavy decisions.
- Do not create a root `CONTEXT.md` unless a future task genuinely needs one. Existing project memory is the canonical domain context.

## Naming

Use the terms already established by project docs: Matrix, Flow, plugin, runtime, bridge, Cline SDK, Signal design system, Whispr, Joplin, task branch, worktree, development integration branch, tracker, and closeout.
