establishing-project-context

1# Establishing Project Context
2 
3## Overview
4 
5Maintain project domain language in `CONTEXT.md` so humans and agents use the
6same canonical terms. This skill is the single active-modeling and write-policy
7owner; it does not own passive glossary reads.
8 
9`CONTEXT.md` is terminology infrastructure, not Aegis governance, architecture,
10requirements, task state, session memory, or runtime authority. Those retain
11their current project owners.
12 
13## Passive Consumption vs Active Modeling
14 
15Passive consumption is a cheap habit of the task-owning workflow:
16 
171. For non-trivial project work, check `CONTEXT-MAP.md`, then relevant root or
18   bounded-context `CONTEXT.md` files when present.
192. Read only relevant active terms and relationships; index first when large.
203. Treat open ambiguities as unresolved data, not active truth.
214. Continue the owning workflow without loading this skill.
22 
23Load this skill only for active modeling when at least one signal exists:
24 
25- a newly resolved domain concept
26- a vague, overloaded, or conflicting term
27- an approved rename, merge, deprecation, or meaning change
28- authority, code, tests, or public language contradict the glossary
29- a deprecated alias re-enters user-visible language
30 
31Tiny factual, status, formatting, or mechanical work performs no context
32ceremony.
33 
34## Location and Safety
35 
36- Single context: `<project-root>/CONTEXT.md`
37- Multiple bounded contexts: root `CONTEXT-MAP.md` maps context names to local
38…