Domain glossary
The domain vocabulary: each term once, with its definition, the words it is also known as and the words to avoid, project-wide or per bounded context.
Terms
The kind is called Term; all the terms of a project together are the Glossary, in the Domain group of the sidebar. A term has a headword, a definition, aka (other names people use) and words to avoid, each with the reason.
A term is project-wide, or belongs to one bounded context when the word means something else elsewhere: an Order in Orders and an Order in Fulfilment can both exist, each in its context.
Where terms show
The Glossary page lists every term with an index by letter and a Context column (Project-wide for a term of no context). A bounded context's Terms tab is the same glossary, filtered to the terms of that context. It is one kind shown in two places.
Agents read terms with spec_get or artefact_list and should use headwords, not the words to avoid.
Keeping the glossary alive
- Add a term when a review thread argues about a word.
- Record the words to avoid with a reason, such as "basket: the UI says cart".
- A term that changes meaning is a change like any other: edit it in a workstream and publish it with the task that needs it.