Rendered from docs/obligations/README.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Obligation records

The documents on this shelf, in the reading order this corpus derives.

The promotion fix has no reading of the assisted fraction — Q4 claims that the promotion fix raises author-attributable edges without more hand entry, and no run supports it.
Declarative voice is called detectable at useful precision, and the sample is unreachable — The three voice categories run over this corpus, and no category reaches the adjudicated sample bar of 50 findings.
The rebuild-and-cache design is measured at spike scale alone — Q6 rules that the graph never rests, and the only evidence is a spike over generated documents.
Working-tree write tools have no measured effect on the assisted fraction — Q7 claims that write tools raise the assisted fraction, and the treatment has never been applied.
A closed-set expectation has no reproducibility reading under grading (discharged) — Q8 claims that a closed-set expectation makes a probe verdict reproducible, and two runs of the one closed-set probe this corpus declares disagree.
Route latency at a harvesting tier is unmeasured — Q9 claims that harvest keeps a solution-tier route query inside 100 ms, and no such tier exists.
No count exists of adopters who stopped at the license terms — Q11 claims that permissive terms remove a step before a trial, and the count that would show it needs a public channel.
An adoption payload has a first reading and no elapsed time — Q12 claims that an adoption payload shrinks, and this repository holds one task that is a day old.
The Shape-origin finding rate is already zero, so the intervention has nowhere to act — Q13 claims that emitted JSON Schema lowers the rate of invalid front matter, and the rate this corpus reports is zero.
The corpus descriptor exists and no probe has run against it (discharged) — A third recording is not refused, and both the discovery and navigability probe categories now carry a verdict against the descriptor. (asserted, and no human has accepted it)
One document has been promoted out of the synthesized tier, and no rate says whether the tier drains — Q15 claims that asserted content moves to accepted rather than accumulates. Both halves of the instrument run, one change has promoted one document, and no rate over time has been read.
The human half of the public presence claim has no instrument at all — Q16 claims that a generated site answers "is this for me?", and only the machine half has an instrument.
No probe tests whether a counted tombstone stops a confident report of absence — Q17 claims a counted tombstone stops a confident report of absence, and the recorder discarded the answer of both runs that reached one.
No probe tests whether an agent reaches the adjudication from the losing document — Q18 claims that an agent meeting the losing document reaches the adjudication, and three of four recorded sessions did, against a mis-specified probe.
Imported edge staleness is unmeasured against scaffolded edges — Q19 claims that imported edges do not decay faster than scaffolded ones, and nothing has been imported.
A cue has no measured effect on traversal precision — Q20 claims that a cue raises traversal precision over the summary fallback, and no campaign has graded one.
Publishing the read set skips a re-run on two of the eighteen merges where the question is live (discharged) — Q21 claims that a published read set lets a gate skip a full re-run on most merges, and the measurement came out against it.
The bundle set is a guess about how adopters cluster — Q3 ships optional content as bundles, and the set of them is a guess that no adopter has revised.
Whether any corpus needs a second export profile — Q17 admits more than one export profile, and the first release ships one unfiltered profile and no second audience.
Whether a solution corpus vendors each source export or references it — Q9 harvests pinned exports, and nothing settles whether the tier above copies each one or points at it.
Emitters 3 through 6 have no named consumer — Q13 stages six emitters, and the last four wait on a consumer that nobody has named.
Whether the transcription projection ships at all — Q19 describes a transcription projection, and no adopter has asked for imported text.
No corpus has authored enough cues to grade — Q20 puts a cue on the referring end, and no corpus has written enough of them to grade.
Whether any corpus other than this one needs a retired-term lexicon — Q21 supplies a retired-term lexicon, and only this repository has ever declared one.
Where the probe kind ships is an unsettled clustering question — Q8 declares a probe kind, and nothing says whether it belongs in the base package or in a bundle.
The operational shape of a hosted server is unstated — Q7 and Q17 both hold the question of who runs a hosted server and how it is deployed, and neither answers it.
What optional holds under the package root — The grammar of $package.optional.forbids is settled and the shape of what it reads is not.
A run cannot report the corpus tree, because nothing computes one — Spec 6 asks every run for a corpus tree beside its findings, and the engine computes none.
What headwater query takes — Spec 6 lists the verb headwater query <expression>, and no document states what an expression is.
The provenance block belongs to the engine, and nothing states its shape — Spec 3 gives the provenance block to the engine and states no shape for it, so a read depends on a key that nothing validates.
List extension in an add-only overlay — A bundle holds no override and no remove, and nothing states whether it may use add_to on a list.
A remove that orphans a name is refused, and the message names the wrong line — Referential integrity finds every orphan a removal leaves, and the finding blames the declaration that reads it rather than the remove.
A required declaration that an overlay may supply cannot be required of a source — The meta-schema has one notion of a required member, and two facet acceptance tests need a second.
Two rules of taxonomy validate name a declaration or an artifact that does not exist — Context safety wants a size budget that no declaration carries, and mapping integrity wants a taxonomy that nothing fetches.
Section contracts in the base — The base specification kind requires two headings, which is a lexical commitment inside a package whose core is semantic.
Identity below the grain of a document — A decision and an obligation are documents now, and a criterion inside a sidecar and a section of a document still reach no identifier index.
The register is not a projection of the lock alone, so generate --check cannot hold it — A rendered register is a function of the corpus, the lock and the clock, and a byte comparison fails on a morning when nobody changed a file.
A corpus that never runs generate --check has no test of a generated-file marker — The census excuses a marked file from every document check, and only generate --check tests that claim.
A participation expectation names one target kind (discharged) — The declaration carried one required to_kind, and the member is optional now. An expectation that names none admits every target kind of its relation.
Composition between two library entries has no add-only form (discharged) — The resolver lets an entry add into an entry it names in requires, orders the pair, and refuses a selection that lacks the named entry.
No declaration expresses a rule about content or state over time — The decision-record tradition holds two invariants over time, and every declaration that carries time is a participation expectation.
A declared invalid_when reaches no check, and two live contradictory decisions pass in silence (discharged) — The base declares conflicts_with with invalid_when, two specifications promise the check, and no code performs it.
Two meta-schema surfaces have a required declaration and no stated form — Ten positions of the meta-schema carry the word gap, where a declaration is required and no form is stated.
A generated index labels a document with its identifier (discharged) — The index of the specification shelf reads HW-SPEC-vision-and-scope where the table it replaced read "Vision and scope".
What {shelf} expands to in a projection output — The base writes output: "{shelf}/README.md", and no document states what the placeholder holds.
The identifier scheme grammar — A scheme holds the prefix that discriminates a kind as a literal inside a pattern string, so no declaration names the prefix that a document IRI would carry.
The scope of a sub-document identifier — An acceptance criterion receives a stable identifier, and nothing says whether it numbers within its requirement or over the corpus.
A mapping key holds a dot, and no address reaches it — facet_values is keyed by a facet and a value joined by a dot, which the reference sublanguage rules ambiguous.
The meta-schema closes eight value sets that nothing states — Eight value sets are closed to the values this corpus writes, and each one is marked guess.
A relation that declares no cardinality has no stated default — Five relations declare no cardinality, and the whole content of the generated check is the default that nothing states.
Downstream delivery of a standards corpus — Spec 7 shares a schema and no corpus content, so a publisher of standards documents reaches a consumer with a rule and never with a document.
A document has no identifier, and every relation target must be one — Spec 3 reserves identifiers for five artifacts and a document is none of them, so every adopter mints a scheme before declaring one edge.
The front-matter key that carries an identifier is undeclared (discharged) — A kind declares an identifier scheme, and nothing states which key in front matter holds the minted value.
The templates and the fixtures of the first library entry disagree with Q4 — The fixture corpus of the first library entry writes a relation at the top level with a path as the target, which Q4 refused.
The tradition has no relation for the link that this corpus makes most — No relation admits a specification-to-specification or an evaluation-to-specification pair, and those are most of this corpus.
A lookup document has no kind, and the shelf layout cannot hold one — The glossary sits on the specification shelf with a layout it cannot satisfy, and it carries a sequence that nothing cites.
A retrofit cannot recover the two dates or the acceptance — Three retrofits have now run, and each one recovered a date only where somebody had recorded one.
No relation records that one argument settled several decisions — The register states twelve times that one evaluation settled several decisions, and no declaration holds that fact.
Kind resolution declares a fourth step that no syntax supports — The fourth step of kind resolution applies a path-pattern refinement, and nothing gives that declaration a form.
"The most specific shelf wins" names no order — Spec 2 rules that the most specific shelf pattern wins, and it never states what makes one pattern more specific.
An anchor resolver normalizes, and nothing states how — Spec 2 requires that anchor strings normalize before comparison, and it states no rule that does it.
A relation may admit a document and an anchor, and no rule orders the two — traces_to takes a document or a code path at the target end, and nothing says which resolver wins a string that both claim.
An anchor that resolves inside a declared exclusion has no stated outcome — Spec 1 fixes three outcomes for an anchor, and a hit inside a corpus exclusion is none of them.
Two identity components are correctness roots that spec 12 does not cover — The anchor resolver has no normalization fixture set asked of it, and the identifier index is absent from the list of roots.
A classified document with no check instance has a third cause — Spec 12 names two causes for a document with zero instances, and the one this corpus met is neither.
A finding names one obligation, and a control discharges a list — Several controls may name one rule, and nothing says which obligation the finding of such a rule names.
A rule that reads the taxonomy has no grain in spec 12's list — Two register rules are about the taxonomy and about no document, and spec 12 draws every scope over the corpus.
The promotion record has three members and no unit, scale or shape — Spec 4 names an observation window, a false-positive threshold and an adjudicated sample, and it gives none of them a form.
A suppressed finding leaves its obligation verified, and spec 4 does not say so — The engine rules that an obligation with accepted deviations against it stays verified, and spec 4 states no such rule.
One of the four warrant values has no instance in this corpus — transcribed is the one warrant with no instance here. asserted acquired nine, so three of the four engine branches now run over corpus content.
A corpus-scoped check makes the coverage rule unreachable (discharged) — A corpus-scoped instance reads every document, and coverage counts routing rather than reading.
A cache of check results does not make a run proportional to the change — Spec 6 promises a run proportional to the change, and a warm run still walks the corpus and builds the whole graph.
The prior version still owes the key edit that the clock has now made (discharged) — The cache key covers the injected clock, and nothing forces whoever adds the prior version to write the matching branch.
A check version is raised by hand, and nothing catches a stale one — Two editions of one rule differ only in code that no digest covers, so a stale version reads the verdicts of the rule before the change.
A participation expectation needs depth one, and Edge does not reach it — Spec 12 calls the neighbourhood scope speculative and offers a test that misses the check that arrived.
A generated check reads its severity from the taxonomy — An adopter moves a generated finding from warn to error by editing data, and spec 12 reads as though only a control is data.
A fragment on a path needs a grain that no scope supplies (discharged) — link.fragment.unresolved read a bare fragment and never one on a path. It reads both at corpus grain now, and the grain it was waiting for was one this engine already had.
Two positions that the meta-schema marks a gap are a closed set in the engine — A voice regime names categories and a language regime names a controlled language, and the language states neither set.
A correctness root that is a type has no failing fixture — Scope enforcement is a type now, and a build that passes is not a fixture that fails.
--changed-only is the content-addressed cache under another name — The warm cache keeps the commit hook just inside its 200 ms budget, and a change-scoped flag stays refused because it hides a verdict input.
A published read set never says which instances must run again — A union of inputs answers whether a verdict survives a merge, and the artifact that answers the finer question is one row per instance.
The lock is half generated and half authored, and nothing states the rule for the seam — The adoption payload is authored and every other line of the lock is derived, and no document says which is which.
The pair grain absorbs a second violation inside one cell — A (document, rule) cell holds every finding of that rule on that document, so a second violation is silent.
Debt that no rule states cannot enter a payload — A corpus with no summaries is unsearchable and has nothing to declare, because a payload holds findings alone.
headwater init cannot reach a package that is not already vendored (discharged) — The first verb a new adopter runs could not complete on a fresh repository, because this engine fetched no package until taxonomy vendor took a location.
An inline quotation reaches every lexical rule as this author's prose (discharged) — The parse now marks an inline quotation, and an unclosed mark suppresses nothing.
fixable has two readings inside one engine (discharged) — One reading says what is true of the defect and the other says what the engine will do about it.
Correcting an identifier is mechanical and it is not local — Spec 12 lists an identifier correction among four mechanical fixes, and no such repair is confined to one document.
A profile names its rules and never states them — ste_house names a controlled language and a profile, and four of its rules are constants in a Rust file.
One rule carries four sub-rules, and a suppression cannot separate them — A directive names a rule, and language.controlled.not_met reports four different defects under one name.
The friction signal that Q4 narrowed is still unread — Q4 keeps a friction signal in a narrower form, and nothing reads the rate at which authors declare one link twice.
How a probe reaches a harvesting tier, and what a transcript costs to keep (discharged) — Q8 leaves the route from a probe to a harvesting tier, the retention policy for transcripts, and who pays for a campaign.
Whether a harvesting tier owes conformance rules of its own — Q9 leaves open whether a harvesting tier has conformance rules, because headwater conformance evaluates one repository.
Where a commercial tier could sit, and how thin the trademark position is — Q11 holds the question of where a commercial tier could sit rather than answering it, and the trademark position is deliberately thin.
Whether the RDF emitter carries owl:inverseOf — An inverse manufactures 332 edges no author declared, which leaves taxonomy audit with no baseline for created_by.
Whether anything is ever promoted out of the asserted tier — Q15 leaves open whether asserted content is promoted as fast as it arrives, and one promotion in this repository cannot answer it.
Whether the four modes of Diátaxis are the kind set for a documentation-site bundle — Q16 leaves the kind set of a documentation-site bundle open, and it is a clustering question that only an adopter settles.
Whether a withheld anchor needs a class beside its count — Q17 counts a withheld anchor, and nothing says whether the count needs a class beside it.
Whether an adjudication is ever partial — Q18 records an adjudication over a pair, and nothing says what happens when each document governs a different axis.
The size of a committed snapshot with full requirement text — Q19 pins an external system of record, and nobody has measured what a snapshot with full requirement text costs.
Whether the read set of a real corpus is small enough that publishing it is free — Publishing the read set costs 0.37 per cent of this corpus, and the fraction is a ratio against document size rather than a constant.
Two documents state what voids a verdict, and they do not agree (discharged) — Spec 12 voids a verdict by a tree diff, and the engine voids it by a hash comparison that no added document reaches.
The front-matter half of a patch has no writer — Three documents name a mechanical correction inside front matter, and the two patch shapes that ship reach a run of prose and a relations block.
A governs edge reaches the path it names and nothing under it (discharged) — Impact detection compares the edited path against the anchor by equality, so an edge onto a directory answers for no file inside it.
Nothing plays the hook role that two relations name as their author (discharged) — Four relations declared created_by: hook and no verb of this engine wrote any of them. From headwater-standard 4.8.0 no relation names hook.
A shelf layout names a file at birth and no rule reads it — A shelf layout is read by the scaffolder and by nothing else, and a rule that read it would report every document that a person renamed or typed by hand.
The base package ships a kind that the scaffolder refuses to write — kinds.specification names no identifier scheme and four relations may name a document of it, so headwater new specification refuses on the stock package and no check reports the cause.
An agent writes the acceptance stamp of every document in this corpus (discharged) — Stop rule 5 forbids an agent to write accepted_by, and 161 of the 161 agent-drafted documents here carry one that the drafting agent typed.
The capture-cost denominator is set by declaration and not by work — Over the eight scaffoldable kinds the verb supplies 48 of 56 units, the one hand entry of each kind is the summary, and the body counts nowhere.
The loss census carries a finding by substring, so an index of rules and paths passes it (discharged) — The audit that holds a format to its loss set asks whether the bytes contain a rule name and a path, and a text report with no findings block at all carried 39 of 45.
The capture-cost surface names an entry point and never the caller — The store records which wire a run of the authoring verb arrived on, and an agent drove both wires on the day the term arrived.
A surface cannot move the assisted fraction of a run (discharged) — The four counts of a reading are derived from the plan, and a plan is the same plan whatever asked for it, so Q7's comparison has to read reach rather than the fraction.
Every check passes a document that is still the scaffolder's placeholder — A decision record whose three sections each read TODO raised no finding at all, and the count over the corpus did not move.
A control that names a sweep marks its obligation verified with nothing run (discharged) — A committed snapshot separates an external control that ran from one that only claims to, and a sweep control discharges nothing without one.
A pinned digest authenticates the pin and never the publisher — A consumer that vendors a package for the first time takes the publisher's identity on the channel that carried the digest, because nothing signs a release and no key reaches an adopter. (warrant proposed is not one of the four values, so no acceptance is read from it)
No anchor resolver reads a committed snapshot, so every imported edge lands unresolved (discharged) — An import writes an edge onto an anchor kind, one resolver ships, and it reads the source tree, so the check layer reports every imported edge as unresolved. (warrant proposed is not one of the four values, so no acceptance is read from it)
A cached verdict about an anchor survives the change that falsifies it (discharged) — The read set of an edge instance holds the declaring document, so a target outside the corpus is in no key and a cached run reports what an uncached run does not. (warrant proposed is not one of the four values, so no acceptance is read from it)
The published read set names no anchor, so a gate decides nothing about one — The read set artifact holds one line per document, so an external anchor is on no line and a gate that compares listed hashes cannot see the target of one leave the tree. (warrant proposed is not one of the four values, so no acceptance is read from it)
An audit reading carries no declared bar, so a distribution cannot become a finding — Of the six readings taxonomy audit takes, one has a number a taxonomy states and five have none, so five report a population and no verdict. (warrant proposed is not one of the four values, so no acceptance is read from it)
No reader takes a waiver against a check finding, so one arm of the escape partition is empty — A waiver mechanism now ships and reads a conformance rule, so the coverage account of headwater check is the one reader of the pair that does not exist. (warrant proposed is not one of the four values, so no acceptance is read from it)
Three conformance rules name an attestation that no record format exists for — Three of the seven conformance rules can never be met, because the attestation each one names has no record format, and four rungs of the ladder wait behind them. (warrant proposed is not one of the four values, so no acceptance is read from it)
Nothing holds the conformance rule set of a package a consumer takes from source (discharged) — A conformance rule set is held by the release digest and never by the lock, so a repository that takes its package from source can edit the rules its own gate reads. (warrant proposed is not one of the four values, so no acceptance is read from it)
A facet that applies to one value of another facet has nowhere to say so — Two rules of the language meet on a facet whose value is the author's judgment, and a sentinel is what the corpus wrote instead. (asserted, and no human has accepted it)
A probe result is printed and never committed, so nothing regenerates one (discharged) — A committed transcript generates a result, regeneration holds the pair, and the result this corpus holds carries a verdict for every probe it graded. (asserted, and no human has accepted it)
Nine documents state a warrant outside the closed set, and only a person can set the value — Spec 3 closes the warrant at four values. Nine documents here state a fifth, and an adoption task holds them until a human sets each value. (asserted, and no human has accepted it)
Every asserted document carries the freshness date that spec 3 says it cannot — Spec 3 rules that an asserted document cannot carry last_verified. The facet contract requires it on every kind that has one, and nine of nine asserted documents carry it. (asserted, and no human has accepted it)
A deletion is invisible where the version that stood there does not parse — A path a change named that no census row holds keeps its prior version only where that version parsed, so a deleted document with malformed front matter reaches no rule. (asserted, and no human has accepted it)
Nothing holds a crate to having a contract under a root that excludes it — Q29 keeps the engine outside the corpus root, so a contract may name a crate and nothing names a crate that has no contract. A participation expectation runs between documents, and an anchor target is no node with a kind. (asserted, and no human has accepted it)
Spec 12 calls two Phase A outcomes structural findings and the engine emits none — Spec 12 lists an unparseable file and an unclassifiable path among the structural findings of Phase A, and the engine emits no finding for either. The census and corpus.classified report both, which is what the control on OB-COV-1 declares, and no document says so. (asserted, and no human has accepted it)
The publication date of this repository is set, and the repository is public (discharged) — Q31 originally left the publication date unset. The owner set 2026-09-08 and opened the repository on 2026-09-06, which discharges this record. (asserted, and no human has accepted it)
The CLI crate wires every verb and carries no tests, so two wiring defects passed a green suite — Two wiring defects in the CLI crate's verb dispatch were found by hand, and reverting either fix still leaves the test suite green.
Survey the wiring decisions of main.rs, verb by verb, and cover the quiet ones — Two more wiring decisions in main.rs went uncovered by hand alone, and the other twenty-seven verbs have never been surveyed for the same failure.
Two test helpers key a scratch directory on the pid alone, and the race springs on the next case added — Two scratch-directory test helpers key on the process id alone, safe only while their files hold one test each.
The comment prose defines by contrast 979 times in 179,000 words, and no mechanism here performs an editorial pass — The comment prose passes every rule this engine has, so the readability problem is a judgment call no check here reaches.
repo-cleanup names one cause for a gone upstream, and this repository produced a second (discharged) — Ancestry misreads a merged branch as unmerged wherever a squash merge or a rewritten history left it unreachable, and git branch -d then refuses on no evidence about content.
Seven rustdoc-relative links in comments point at pages the doc tree does not have — Seven links in engine comments are written for rustdoc output that no job ever builds, so nothing has ever resolved them.
A British spelling reaches a serialized grain string, so the rename is a corpus change and a derived-bytes change at once — A British spelling in the serialized grain string entangles a prose rename with cached verdicts, a read-set artifact, and recorded fixtures.
The rest of the editorial pass, with cli/src/main.rs at the head of the distribution — The editorial pass measured 180,255 words of comment prose and rewrote two files, leaving cli/src/main.rs, the largest, untouched.
An identifier scheme glues three parts into one string, so nothing can decide that two schemes are disjoint — A pattern string glues the prefix, the namespace, and the local part, so disjointness is undecided and a published address is invented from its path.
A check can meet the failing-fixture bar with a fixture that cannot distinguish the rule from its neighbour — A fixture set can meet the failing-fixture bar in full and never exercise the choice between a rule and its neighbor.
An identifier scheme names no prefix, so an RDF projection derives a document IRI from a file path — The gap HW-OBL-0046 left open, a document IRI built from a file path rather than a name, is gated on a consumer for rdf or skos that has not appeared.
The obligation register states its own size by hand, and it went stale three times in two days (discharged) — Spec 13 named its own counts by hand and named its list membership by hand, and both drifted. A fixture now holds both in both directions, and spec 13 states neither as a number.
A specification sentence closes a set with a count the source exceeds, and 115 of 127 candidates are unchecked — Three sentences that closed a set with a wrong count were found by accident, and 115 more candidates were never checked.
The cache-identity test reads the live working tree, so an edit during the run reports the correctness root as violated — The test proving cache and no-cache agree on a verdict reads the live working tree, and a concurrent edit reports the correctness root as violated.
The Stop hook reads its re-entry guard with an interpreter it does not require, so a machine with no python3 re-blocks the same turn (discharged) — The Stop hook reads its re-entry guard through python3 with no fallback, so a machine without python3 re-blocks the same turn.
The help assertion never asks a subcommand, and no rust-version declares the floor clap now sits on — The help test pins only the root command, and no machine-readable rust-version stops clap's own margin from reaching zero.
The write-time hook still picks pointer lines out of prose by their em dash (discharged) — The write-time hook still finds pointer lines by grepping for an em dash, so a document with no summary drops out in silence.
A current decision declares no required edge to the document it settled, so 22 of 23 reach no specification at all — 22 of 23 current decisions declare no edge to the specification they settled, and one declares no relation at all.
The glossary's Package entry omits conformance and still lists plugins, which #367 dropped (discharged) — The glossary's Package entry is missing conformance and still names plugins, a key that spec 7 does not declare.
Ledger::render() in adoption.rs has the same zero-count defect suppression.rs had before PR #450, still latent — adoption.rs::Ledger::render() drops its own header and count line whenever a corpus declares no adoption debt, the same shape PR #450 fixed in suppression.rs, and nothing reads the dropped text yet.
The rewritten sentence splitter has no dedicated conformance fixtures — The sentence splitter has inline tests, but it has no data-driven corpus that preserves the failures behind Q5's rewrite. (asserted, and no human has accepted it)
The adoption decay section is fixture-recorded only in its empty shape — Every section of the recorded audit report renders populated except the adoption one, whose fixture tree declares no payload.
probe's fourteen refusals have no coverage test, and three of them are named by no test at all — Three of the probe crate's fourteen refusals are named by no test, and no case holds the set to its own coverage.
A help string and the interface contract that restates it can both be false with the whole suite green — Two suites read the shape of the help and the headings of the contract, and neither reads a word of either.
The capture report says two denominators over a store that named seventeen taxonomies — The capture report warns that its aggregate crosses two denominators, on a run whose own next line lists seventeen of them.
clap owns the help flag, so -h, --help reads Print help on all 32 verb pages — The fifth entry of the GLOBALS table carries clap's own two words rather than a description this repository wrote, because clap adds its help argument after the point where a caller can name it.
A sentence that opens with a hash and an issue number is folded into the sentence before it (discharged) — opens_a_sentence admits a digit and not a hash, so a sentence that cites an issue as #346 is counted with the sentence before it and reported at their combined length. (asserted, and no human has accepted it)
The generated half of the site loads highlight.js from a third party with no subresource integrity (discharged) — 325 generated pages loaded highlight.js and two stylesheets from cdnjs with no integrity attribute. The theme option is off, a guarded color-mode script replaces the one that threw without those elements, and no served page names that origin. (asserted, and no human has accepted it)
The validation block of mkdocs.yml is a gate this repository owns and no fixture drives — Two raised severities in mkdocs.yml are the whole of two gates, and no case in this repository fails when either one is lowered
Spec 7 prints a package version that no check compares with the recipe (discharged) — Spec 7's assembly example and the shipped recipe both pin one package version, and nothing compares them. The example was stale for four minor versions and no rule, no fixture and no CI job reported it. (asserted, and no human has accepted it)
Ten decision records claim a Q number the decision register does not carry — Ten decision records name a Q number in their file name that docs/spec/09-decisions.md has no section for, and nothing reads either side of the pair. (asserted, and no human has accepted it)
The regeneration check tests byte equality before the marker, so a file the census stopped counting as generated still passes — generate --check reads byte equality before it reads the marker, so a generated file the census dropped from the generated set still passes it
A rendered-page gate greps for a string it requires and states no denominator, so an empty build passes it — The CI step that holds every rendered page to a corpus pointer exits 0 over a served directory with no page in it
Spec 2 states a corpus-wide default language regime that no rule of this engine reads — Spec 2 tells an adopter that a corpus declares one default language regime. The engine resolves a regime through a kind and implements no fallback, so the first half of that sentence describes nothing. (asserted, and no human has accepted it)
The default branch requires no approving review, which is the condition HW-DR-0034 named as reopening it — The ruleset on the default branch requires zero approving reviews, which is the posture HW-DR-0034 named as the thing that erases its line. The corpus owes a ruling. (asserted, and no human has accepted it)
A saturated pattern set and a clean corpus are the same zero, and no report separates them — The voice rule reports zero because not one of its forty patterns occurs here, and that reads the same as a clean corpus. (asserted, and no human has accepted it)
The coverage report lists one path twice, so the self-assessment page publishes two unaccounted files where one exists (discharged) — Coverage::of now lists each unaccounted path once and exempts the claim store by name, so coverage.unaccounted reads [] and the self-assessment page publishes 0. (asserted, and no human has accepted it)
The blank facet value rule reaches no obligation so the report names none (discharged) — Every other rule this engine carries reaches one obligation. facet.value.blank reaches none, because the control that would bind it sits in the vendored package and the edit moves the pin digest. (asserted, and no human has accepted it)
No rule reads a document facet value against the type its declaration states — A facet declares type: date, type: integer or type: string, and no check reads a document's value against that declaration. A mapping where a date belongs reaches a strict run at exit 0. (asserted, and no human has accepted it)
Nine hand-kept constants enumerate an enum and nothing holds one against the variants — Nine constants named ALL type the variant list of an enum by hand, the array length is part of the type, and no assertion compares either against the exhaustive match beside it. (asserted, and no human has accepted it)
Publishing the base package reports 51 references that resolve nowhere and exits 0 (discharged) — Publishing headwater/standard 4.1.0 prints that the artifact records 51 references resolving nowhere inside it, exits 0, ships the list in the manifest, and taxonomy vendor installs it without a word. (asserted, and no human has accepted it)
Two documents take one sequence on a sequence-declaring shelf and no rule reads it — Two design specs declaring sequence 16, whose file names both open with 16-, give check --strict exit 0 and the same finding count as the tree without them. (asserted, and no human has accepted it)
A blessed fixture is read by a sibling case that runs while the write truncates it (discharged) — Under HEADWATER_BLESS one case truncates crates/conformance/fixtures/wrapped.report while a sibling thread of the same binary reads it, which can panic the run and cannot corrupt the artifact. (asserted, and no human has accepted it)
The every-instance report detail reaches four test files and no caller outside them — The check runner declares a report detail that prints every check instance, and only four test targets ever select it, because no flag and no library consumer can. (asserted, and no human has accepted it)
The commit gate checks prose with a binary it never compares against the engine sources — The prose clause of the commit gate runs a binary it never compares against the engine sources. The figures clause that did ask left the gate in #1273. (asserted, and no human has accepted it)
A renderer's color mode is wired at a call site that no type forbids from being wrong — A caller that passes the plain color mode forever is a defect that no type and no piped test can report. (asserted, and no human has accepted it)
An unresolved prose link reaches a run as a graph fact and no rule turns it into a finding (discharged) — A link in prose whose target path is absent is counted in the graph section of a run and reaches no rule. So it never becomes a finding and never fails a strict run. (asserted, and no human has accepted it)
The publish-crates retry loop has no retry ceiling — publish_with_retry retries a 429 forever, so GitHub Actions' unstated default timeout is its only ceiling, and nobody has measured it. (asserted, and no human has accepted it)
No mechanism holds a committed binary asset against a run — The recording thread of this record is narrowed by HW-DR-0078: disclosure, not a compare, closes #601's binary asset. What holds a DIFFERENT committed binary asset against a run, one with no ruling of its own, is still nothing. (asserted, and no human has accepted it)
Nothing states why the vendored package root is visible in an adopter tree (discharged) — Issue #381 ruled where doctrine lands inside a package and gave three reasons, none about visibility. The root moved under .headwater/ on a ruling and not on that measurement, which HW-DR-0067 states. (asserted, and no human has accepted it)
Whether an admitted library entry may require a bundle that admission refuses — An entry the canonical library refuses is required by two entries it admits, and no criterion and no ruling reads that direction (asserted, and no human has accepted it)
A facet-only entry has no kind, and the entry anatomy asks for two things that presume one (discharged) — HW-DR-0079 rules the templates half, and criterion 4 now says a facet-only entry's corpus borrows a kind and demonstrates the facet, not the kind. (asserted, and no human has accepted it)
The registered-deviation edge of the compliance tradition cannot be declared — Spec 2 names a registered-deviation check on does_not_comply_with, and no entry can enable or declare that relation. (asserted, and no human has accepted it)
The negative compliance edge and the governance precedence clause contradict — Spec 2 puts does_not_comply_with in the governance family and spells it from the deviating document, so the violator governs the standard. (asserted, and no human has accepted it)
A base shelf path is closed to every later entry over the same ground — The base claims docs/specifications/** for one shelf, and shelf determinism then refuses every later entry the path its own tradition uses. (asserted, and no human has accepted it)
A voice regime carries a forbid list, so a normative keyword rule has no form — A voice regime carries a forbid list and nothing else, so a rule that every requirement uses a normative keyword has no declarable form. (asserted, and no human has accepted it)
An unknown discriminator value removes a document from every check and no gate reports it — A document whose discriminator value names no kind leaves every check, the census still carries the row, and a strict run exits 0. (asserted, and no human has accepted it)
Assumptions that a library entry takes where the specification does not speak — A shelf layout, a stable volatility, an identifier scheme with no namespace and an expectation window are readings that no document covers. (asserted, and no human has accepted it)
Admission criterion 5 has no reading for an entry that serves neither core purpose (discharged) — HW-DR-0079 rules that a full entry names or extends a core-serving kind, and states which reading each of the three affected entries takes. (asserted, and no human has accepted it)
The base ships one voice regime and a prospective document has none — The base carries voice.declarative alone, and it forbids future_intent, so a corpus of requirements on the bare base reports its own tradition. (asserted, and no human has accepted it)
A requirement has no identity, so a descoped requirement has no form — A descoped requirement is a state of one line inside a document, and a line has no identity here. (asserted, and no human has accepted it)
A relation writes a state onto a kind that binds no lifecycle regime and nothing reads that pair — A rule reads on_target.set_state, and it skips a kind that binds no lifecycle regime and can stand in no state. (asserted, and no human has accepted it)
A superseded document claims no reliance, and nothing measures whether a session honors that (discharged) — A supersession says that nobody may rely on the document that lost, and every mechanism here acts on a relation rather than on a reading. (asserted, and no human has accepted it)
Nothing states how much of a session's budget the standing instructions consume before work starts (discharged) — Every session loads standing instructions before any task begins. The #1384 batch measured this repository's share at a median of 7,225 tokens, and spec 5 states it. (asserted, and no human has accepted it)
An observation snapshot records a commit and nothing reads it back (discharged) — Discharged by the owner's ruling on issue 937. An observation's commit is provenance, and the engine never reads its ancestry. The standard taxonomy states that the adopter's process keeps it honest.
Three graded regression runs are owed a fresh recording against a moved taxonomy lock — Three current probe-run transcripts moved to deprecated when a taxonomy change staled their lock, and no fresh session has run against the new one. (asserted, and no human has accepted it)
No coverage or mutation measurement has ever been taken over the engine's test suite — 1233 tests exist under engine/crates and nobody has measured whether they would catch a defect, with cargo-llvm-cov and cargo-mutants as the named, unrun instruments.
docs/decisions/0077 still describes HW-DR-0049's rewrite as pending, after #574 made it (discharged) — Decision 0077 called HW-DR-0049's rewrite pending after #574 made it. #1070 rewrote that sentence, and the record waits only for its move to discharged.
Two sample counts, HW-OBL-0002's and voice.rs's own census, predate the scent-role fix and need retaking (discharged) — HW-OBL-0002 and the voice.rs census now carry the reading of 2026-09-27, taken over the body and the summary facet that the scent-role fix #774 added.
Four small test and wording gaps from run 20260923-0733 filed together — A collation opener class, a cache key's CLI wiring, a cache doc word and a recurring board-card gap, each with no reader outside this repository.
The commit gate does not see docs/taxonomies/README.md drift from its vendored copy — Only the required Engine tests job catches a drift between the taxonomy bundles and their vendored copy. So a contributor learns of it at CI and not at commit.
A bless run of the conformance render tests races two tests over one fixture file (discharged) — Under HEADWATER_BLESS=1, one render test reads fixtures/wrapped.report while a sibling test in the same process rewrites it, and the reader can panic.
The opening sentence of the self-found list in spec 13 counts forty-nine items in ranges that do not match the list (discharged) — Spec 13 opened its self-found list with a count of forty-nine items in five ranges that the list did not match. The sentence now states no count and no range, and a fixture fails on a prose line of spec 13 that does.
Ten rules of the editions ledger have one recorded corpus, so a rule change blessed with an edit to that corpus passes — A bless of the editions ledger re-records any row whose corpus moved. So a rule change needs no VERSION raise when it edits each corpus whose verdicts it moves. Ten of 31 rules have one corpus.
No run measures whether the documents under docs change what an agent builds (discharged) — The campaign's absent arm keeps docs/, so no rate says whether the documents change what an agent builds. The documentation tier removes them, and nobody has paid for a run of it. (asserted, and no human has accepted it)
Six corpus gaps from run 20260929-1205, filed together — Run 20260929-1205 surfaced six findings about this corpus's own edges, stamps and wording, none with a reader outside this repository. This record files them together under the intake cap.
The subsystem specs claim evidence their targets do not carry, and two rules of the shelf live only in a test — Seven subsystem specs claim evidenced over asserted targets. HW-DR-0098 does not link the measurement spec. Only subsystem_map.rs states that a spec governs exactly its crates' src trees.
The counterfactual campaign evaluation withholds its discharges edge until a person promotes it — The evaluation of the 2026-09-30 counterfactual campaign is warrant asserted, so the discharges edge onto HW-OBL-0223 and HW-OBL-0197 waits on a person promoting it.
Comments in the command-surface crates and their subsystem spec state eight stale facts — Eight comments in cli, paint, generate, probe, sweep and the command-surface subsystem spec state facts the code no longer holds, found by the builds and verifies of run 20261001-1107.

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