Maintain Domain Glossary

Output

{
  "status": "ok" | "error",
  "entries": [
    {
      "term": "<Term>",
      "definition": "<one sentence, plain language>",
      "status": "active" | "deprecated",
      "replaces": "<term or null>",
      "change_reason": "<reason if updated or deprecated, null if new>"
    }
  ],
  "markdown": "<full glossary.md content>",
  "error": "<error message or null>"
}

Process

1. Collect all terms from Four-Color Model objects and Context Map context names.
2. For each term:
   • If it does not exist in the glossary, create a new entry.
   • If it already exists and the definition is unchanged, keep as-is.
   • If it already exists and the definition would change, apply Chesterton's Fence: record the previous definition and the reason for the change in change_reason.
3. Detect synonyms: if two terms refer to the same concept, flag them. Propose keeping one and deprecating the other. Do not auto-resolve — present to Domain Expert.
4. Sort entries alphabetically.
5. Generate markdown output.

Markdown Output Format

# Domain Glossary

> Last updated: <YYYY-MM-DD>
> All terms in this glossary constitute the Ubiquitous Language of this project.
> No synonyms. No informal aliases.

---

**Customer** — A role played by a Person who has placed at least one Order.

**Order** — A moment-interval representing a customer's request to purchase one or more Products.

**ProductSpec** — A description defining the attributes, pricing rules, and availability of a product offering.

---

## Deprecated Terms

**Buyer** _(deprecated — use Customer)_ — Previously used to refer to the purchasing party. Replaced by Customer for consistency with the Order context ubiquitous language.

Validation