Domain Language Authority Grill Status

Branch Dashboard

Branch: Domain-language authority and promotion
Completion: 100%
Locked direction: Open grills propose terminology. User-accepted closed grills promote accepted terminology into the stable routed wiki glossary, which is the canonical domain context.
Still open: none
Parked branches: downstream skill integration, bounded-context mapping, compatibility projection, migration, and stale-code enforcement

Question id	Prerequisites	Question	State
—	—	No unanswered decisions remain	answered

Proposed Term: A domain term recorded by an open grill that has not yet entered the canonical glossary. Avoid: canonical term, accepted term
Canonical Domain Context: The stable routed wiki glossary containing the currently accepted domain language. Avoid: grill glossary, session glossary
Promotion: The controlled transfer of accepted terminology from a closed grill into the Canonical Domain Context. Avoid: sync, copy
Bounded Context: A business-language boundary within which each canonical term has one consistent meaning. Avoid: workspace, package, folder

A Requirements Grill proposes zero or more Proposed Terms.
Promotion moves accepted Proposed Terms into exactly one relevant Canonical Domain Context.
A Canonical Domain Context represents exactly one Bounded Context.

Open grill terminology is not canonical.
Promotion occurs only after explicit acceptance of the closed grill.
Detailed grill artifacts remain history and never override the Canonical Domain Context after promotion.
A glossary conflict always requires explicit user resolution.
Concurrent grills are isolated by separate branches and worktrees; this workflow does not design concurrent promotion.
requirements-grill invokes domain-modeling and does not duplicate its terminology criteria.
Domain-modeling persists through the active grill glossary and the accepted closure promotion path, not through a separate root file.

"Our glossary.md" means the stable routed wiki glossary for a bounded context; no root GLOSSARY.md is part of the accepted initial model.
Existing apps/wiki/content/docs/project/domains/ pages are domain source indexes. Canonical glossaries use <context>-glossary.mdx, and the domain index acts as the context map.
Direct domain-modeling invocation and promotion failure behavior are outside the accepted scope.
Existing CLI and Harness documentation domains are not DDD bounded contexts.
Matt Pocock's imported skill is the sole behavior authority; Harness owns only integration and persistence routing.
The imported skill is pinned with license and provenance; requirements-grill loads it before the first question and keeps it active through closure; wiki synthesis owns accepted-term promotion.