Build (or refine) this project's CONTEXT.md with me. Explore the codebase first to assemble a candidate term list, then interview me through it one item at a time — proposing a canonical name, a one-sentence definition, and aliases to avoid, with your recommendation stated for each.

Modify CONTEXT.md only when I confirm an item or we agree the language has been properly decomposed. Never write unconfirmed material into the file.

Which file

Follow the single/multi-context conventions in CONTEXT-FORMAT.md:

CONTEXT-MAP.md at the root → multiple contexts; ask which context the session covers if it isn't obvious
root CONTEXT.md only → single context
neither → single context; create CONTEXT.md lazily when the first term is confirmed

If a CONTEXT.md already exists, read it before exploring. The session then covers both gaps (concepts in the code but missing from the glossary) and staleness (entries that no longer match the code or that I contradict when questioned).

create-context

Which file