ubiquitous-language

To extract a domain glossary from live dialogue, mine the conversation for domain-relevant nouns, verbs, and concepts, resolving synonyms and overloaded terms into canonical entries. The extracted terminology is then persisted to a markdown file for continuous reuse across sessions.

Resolving synonyms and overloaded terms when building a domain glossary involves identifying collisions, flagging ambiguities, and proposing canonical terms with explicit aliases. This opinionated approach ensures a stable, unambiguous vocabulary for your project.

When re-invoking the glossary extraction process, it refines the existing file in place rather than overwriting it. This behavior incorporates new terms while maintaining historical context and updating definitions to reflect the latest dialogue.

Yes, you can persist domain terminology across multiple sessions by saving the canonical glossary to a dedicated markdown file. Subsequent sessions automatically inherit this stable vocabulary, ensuring consistent communication and documentation.

Use ubiquitous language extraction when you need to harden domain terminology, build a glossary from scratch, or surface new concepts from conversations that lack formal documentation. It is particularly useful for establishing a shared, canonical vocabulary early in a project.

The extracted domain glossary follows an explicit format defined in a dedicated reference markdown file. This structure ensures consistent term canonicalization, recording decisions with inline recommendations for future reference and maintenance.