Glossary term
A word of the shared business language, with its definition and the words to avoid.
What it is
A glossary term fixes what a word means in this project: what an "appointment" is, how it differs from a "slot" and a "booking", and which words not to use for it.
Why it matters
Many requirement misunderstandings are really vocabulary misunderstandings. When the business says "booking" and the code says "reservation" and the database says "event", every conversation needs a translator.
What goes wrong without it
- The same thing has three names in code, screens and documents.
- Two different things share one name, and requirements are read two ways.
What it gives an AI agent
Agents name things constantly — variables, tables, screen texts. A glossary makes them use the business's words, so code, UI and requirements stay readable to each other.
Example: Clinic Booking
| Weak | Strong |
|---|---|
| Booking — the thing patients make. | Appointment: a patient's confirmed time with a clinician. Not "booking" or "reservation". A slot is a free time; an appointment fills it. |
How it relates to the rest
- Used in requirements, criteria and screen texts.
- Can be account-wide, shared by every project.
In Corpole
- Type Glossary term (TRM). Statuses: Draft, Active, Retired.
- People write terms; agents read them.