🜄Headwater

How it works Compare Proof Tutorial

Obligation records

Publishing the base package reports 51 references that resolve nowhere and exits 0
Two documents take one sequence on a sequence-declaring shelf and no rule reads it
A blessed fixture is read by a sibling case that runs while the write truncates it
The every-instance report detail reaches four test files and no caller outside them
The commit gate checks prose with a binary it never compares against the engine sources
A renderer's color mode is wired at a call site that no type forbids from being wrong
An unresolved prose link reaches a run as a graph fact and no rule turns it into a finding
The publish-crates retry loop has no retry ceiling
No mechanism holds a committed binary asset against a run
Nothing states why the vendored package root is visible in an adopter tree
Whether an admitted library entry may require a bundle that admission refuses
A facet-only entry has no kind, and the entry anatomy asks for two things that presume one
The registered-deviation edge of the compliance tradition cannot be declared
The negative compliance edge and the governance precedence clause contradict
A base shelf path is closed to every later entry over the same ground
A voice regime carries a forbid list, so a normative keyword rule has no form
An unknown discriminator value removes a document from every check and no gate reports it
Assumptions that a library entry takes where the specification does not speak
Admission criterion 5 has no reading for an entry that serves neither core purpose
The base ships one voice regime and a prospective document has none
A requirement has no identity, so a descoped requirement has no form
A relation writes a state onto a kind that binds no lifecycle regime and nothing reads that pair
A superseded document claims no reliance, and nothing measures whether a session honors that
Nothing states how much of a session's budget the standing instructions consume before work starts
An observation snapshot records a commit and nothing reads it back
Three graded regression runs are owed a fresh recording against a moved taxonomy lock
No coverage or mutation measurement has ever been taken over the engine's test suite
docs/decisions/0077 still describes HW-DR-0049's rewrite as pending, after #574 made it
Two sample counts, HW-OBL-0002's and voice.rs's own census, predate the scent-role fix and need retaking
Four small test and wording gaps from run 20260923-0733 filed together

All 209 on this shelf →

Rendered from docs/obligations/0190-a-voice-regime-carries-a-forbid-list-so-a-normative-keyword-rule-has-no-form.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A voice regime carries a forbid list, so a normative keyword rule has no form

Context

Spec 2's worked example promises "normative keywords on standards" for the product-suite column, and "mandatory normative keyword usage" for the regulated one. A voice regime carries a forbid list and nothing else.

A rule that every normative sentence uses one of a fixed keyword set is the opposite shape. It is a requirement to use a word rather than a refusal to use one. The standards-spec entry binds declarative on all three of its kinds and states the gap. Its fourth finding at line 158 holds the argument. A standard whose requirements avoid every normative keyword passes every rule that this language can write.

Obligation

The owner owes a form for a positive lexical requirement, or a correction to the worked example that promises one. An adopter who takes a standards taxonomy to hold a corpus to RFC 2119 keywords takes a regime that cannot express the rule. The promise in the worked example is what such an adopter reads first.

Discharge

This record discharges when a voice regime carries a require list beside its forbid list, with a check behind it. It discharges the other way when spec 2 states that a positive keyword rule is out of scope. The worked example then drops the promise.

Keys	Action
`?`	Open this help
`n`	Next page
`p`	Previous page
`s`	Search