Project Context
Resolve ambiguous names and conflicting facts against current code, project instructions, and the user's intended meaning. Separate domain concepts from implementation labels; make important relationships and invariants explicit.
Prefer the existing glossary or documentation owner. If a concise context file would prevent repeated confusion, propose or maintain it within the authorized scope; .do-it/CONTEXT.md is one possible home, not a required authority.
Keep stable project facts, temporary assumptions, and task progress distinguishable. Include only terms that help decisions, with source links when useful. Update consumers of renamed concepts without inventing a second source of truth.