ubiquitous-language

To extract domain terminology into a glossary, provide a conversation log to the system. It identifies domain terms, flags ambiguities, proposes canonical terms, and saves the formalized output as a UBIQUITOUS_LANGUAGE.md file.

A ubiquitous language glossary aligns stakeholders by reducing terminology ambiguity across product design and engineering workflows. It captures canonical domain terms to ensure consistent communication and shared understanding during domain modeling.

You align ambiguous domain terms by processing team discussions to identify conflicting definitions. The system flags these ambiguities, proposes canonical terms, and generates a shared glossary file to synchronize stakeholder understanding.

Yes, you can update an existing glossary with new terms. The system maintains an evolving terminology record by processing new conversation logs, appending new domain terms, and updating previously flagged ambiguities in the output file.

Generating a ubiquitous language glossary requires no external dependencies. You only need to provide the raw conversation log containing the domain terms; the system autonomously extracts and formalizes the terminology into a markdown file.