domain-modeling

To standardize project terminology, maintain a single CONTEXT.md glossary that anchors terms with precise definitions, clear relationships, and flagged ambiguities to resolve naming drift across teams.

Resolving domain modeling ambiguities during onboarding requires a canonical vocabulary glossary that defines fuzzy terms, standardizes multiple names for the same concept, and clarifies relationships to ensure consistent interpretation.

Create a CONTEXT.md file by lazily initializing it when a new term crystallizes, structuring entries with language rules, term relationships, and flagged ambiguities to maintain a single source of truth.

You need a living glossary for domain shifts when terms are fuzzy, concepts are renamed, or new modules are introduced, ensuring the project vocabulary remains consistent across code, docs, and conversations.

Yes, glossary discipline works without external dependencies by enforcing CONTEXT.md structure internally, relying solely on markdown formatting to document language rules, relationships, and ambiguities.

Vocabulary drift happens in cross-team collaboration when multiple names describe the same concept without a canonical glossary, causing inconsistent naming and interpretation across code and documentation.