Rendered from docs/obligations/0078-two-positions-that-the-meta-schema-marks-a-gap-are-a-closed.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Two positions that the meta-schema marks a gap are a closed set in the engine

Context

voice_regime.forbid names categories and states no set of them. language_regime.controlled names a controlled language and states no set either. A check needs a pattern set for each category and a rule set for each profile, and the language holds neither.

Obligation

What is open is whether the language should carry the sets, because an adopter who adds a category today waits for a build.

Discharge

So the engine carries a closed set of both, and an instance that meets a name outside it skips with that name in the reason. The skip reports the gap once per document rather than once per release.