establishing-project-context

# Establishing Project Context ## Overview Maintain a `CONTEXT.md` file at the project root that defines the project's domain language — a single source of truth for terminology shared between the agent and the human. Borrowed from Domain-Driven Design's "ubiquitous language" principle. CONTEXT.md is about the user's project domain, NOT about Aegis governance. For Aegis governance docs, see `docs/current/` and `docs/adr/`. ## Where CONTEXT.md Lives - **Single project**: `<project_root>/CONTEXT.md` - **Monorepo / multiple bounded contexts**: `<project_root>/CONTEXT-MAP.md` maps context names to their locations: ``` ordering → src/ordering/CONTEXT.md billing → src/billing/CONTEXT.md ``` System-wide terms still go in root `CONTEXT.md`. Create files lazily — only when you have something to write. ## When to Use **On first entering a project:** 1. Check if `CONTEXT.md` (or `CONTEXT-MAP.md`) exists 2. If not, ask briefly: "Want me to set up a shared language glossary for this project?" 3. If yes, start with 3-5 core domain terms, then iterate **During brainstorming / planning / debugging:** - When user uses a vague or overloaded term, propose a precise canonical term - Check against existing CONTEXT.md glossary before proposing - Write each term resolution immediately — don't batch ## CONTEXT.md Format See `CONTEXT-FORMAT.md` in this directory for the canonical template. Key rules: - Only include terms meaningful to domain experts - Don't couple CONTEXT.m...