Context
Lane 6 of the AI Hero course vetting (issue #2904) adopted seven terms into the project's ubiquitous language — primary source / secondary source, phase boundary, smart zone, AFK criterion, asset rush, context load / cognitive load, navigation pointer — with decisions and definitions-by-basis recorded in docs/upstream/aihero-course.md ("Term adoption"). Glossary materialization was routed through /domain-driven-design:curate-language per the contract, but its convention-resolution ladder found NO existing glossary and more than one plausible placement (a flat docs/GLOSSARY.md beside CATALOG.md, or a docs/conventions/ entry), and the lane ran unattended — so per the glossary contract ("defer creation and report the missing convention rather than baking in a universal filename or path") creation was deferred rather than invented.
Proposed work
- Decide the glossary's home and shape with the maintainer (the one open question), then create it via
/domain-driven-design:curate-language with the seven adopted terms — one canonical term per concept, 1–2 sentence definitions, rejected synonyms per the lane's REJECT rows (design concept → shared understanding; sediment; cache; highway/stale highway; sycophancy; grill-execute-clear; push vs point → point, don't copy).
- Cross-link the glossary from
docs/upstream/aihero-course.md's term-adoption section once it exists.
Acceptance criteria
References
Metadata
| Field |
Value |
| Category |
unspecified |
| Area |
docs |
| Ecosystem |
unspecified |
Context
Lane 6 of the AI Hero course vetting (issue #2904) adopted seven terms into the project's ubiquitous language — primary source / secondary source, phase boundary, smart zone, AFK criterion, asset rush, context load / cognitive load, navigation pointer — with decisions and definitions-by-basis recorded in
docs/upstream/aihero-course.md("Term adoption"). Glossary materialization was routed through/domain-driven-design:curate-languageper the contract, but its convention-resolution ladder found NO existing glossary and more than one plausible placement (a flatdocs/GLOSSARY.mdbeside CATALOG.md, or adocs/conventions/entry), and the lane ran unattended — so per the glossary contract ("defer creation and report the missing convention rather than baking in a universal filename or path") creation was deferred rather than invented.Proposed work
/domain-driven-design:curate-languagewith the seven adopted terms — one canonical term per concept, 1–2 sentence definitions, rejected synonyms per the lane's REJECT rows (design concept → shared understanding; sediment; cache; highway/stale highway; sycophancy; grill-execute-clear; push vs point → point, don't copy).docs/upstream/aihero-course.md's term-adoption section once it exists.Acceptance criteria
docs/upstream/aihero-course.mdterm-adoption section links the glossaryReferences
docs/upstream/aihero-course.md("Term adoption" section — the decision record)plugins/domain-driven-design/skills/curate-language/context/glossary-contract.md(entry discipline + convention ladder)Metadata