🜄Headwater

How it works Compare Proof Tutorial

Obligation records

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
The commit gate does not see docs/taxonomies/README.md drift from its vendored copy
A bless run of the conformance render tests races two tests over one fixture file
The opening sentence of the self-found list in spec 13 counts forty-nine items in ranges that do not match the list
Ten rules of the editions ledger have one recorded corpus, so a rule change blessed with an edit to that corpus passes

All 209 on this shelf →

Rendered from docs/obligations/0194-the-base-ships-one-voice-regime-and-a-prospective-document-has-none.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

The base ships one voice regime and a prospective document has none

Context

The base package carries one voice regime, which is voice.declarative, and it forbids future_intent. A requirements document states what a product must do before the product exists, so it is prospective by definition.

The brd-prd entry therefore declares regimes.voice.prospective, on the narrative precedent that the design-spec entry set. Its fixture corpus measures what declarative would have reported over the same prose: four extra findings across four of seven documents. The second finding at line 165 holds the run.

Obligation

An adopter who takes the bare base has no voice regime under which a requirements document can say what a product must do. A corpus of requirements on the base reports its own tradition as a finding, four times in seven documents by the one measurement there is.

Two entries have now added a voice regime that the base does not carry. So the base carries one regime and the language needs at least two, and nothing states which ones belong in a minimal base. Q3 is the ruling that made the base minimal, and it did not measure this case.

Discharge

This record discharges when the base carries a prospective voice regime. It discharges the other way when a decision names the bundle that a prospective corpus takes. A ruling that every adopter writes their own regime discharges it too. The base then says so where an adopter meets the one regime it has.

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