Rendered from docs/obligations/0226-six-corpus-gaps-from-run-20260929-1205-filed-together.md in the Headwater
corpus. Every document on this half of the site is typed by the taxonomy
the descriptor names: corpus.json.
Six corpus gaps from run 20260929-1205, filed together
Context
hw-run-policy caps what one pass sends to this register as full records. Past the cap, one record lists the rest. Run 20260929-1205 wrote six intake lines about this corpus's own edges, stamps and wording. The product owner ruled each one RECORD, on the tenth-merge pass and the end-of-run pass of that run. None names a reader outside this repository. Each item below gives the stage that found it and the issue in hand at the time.
Obligation
Edges that a person types. Each relation below is created_by: agent, so an agent may not write it, and HW-DR-0083 leaves it to a person.
- HW-DR-0094 rests its Context on HW-DR-0097 in prose and declares no
traces_to: HW-DR-0097edge. (build, #1339) - HW-DR-0099 names line 188 of
docs/evaluations/graph-export-and-federation.mdas superseded in prose only. It declares notraces_toedge to HW-EVAL-graph-export-and-federation. (build, #1368)
Stamps.
- HW-OBL-0062 gained a Discharge sentence in #1412 on 2026-09-29 and keeps
last_verified: 2026-08-13. No rule says whether a content edit to an open obligation owes a new re-verification stamp. (build, #1410) - Row 20 of
docs/reviews/the-sixty-four-restored-help-strings-checked-against-the-binary.mdquotes the help text ofexport --atfrom before #1343. The review is a point-in-time record and stays as written. Nothing re-checks a help string that a review recorded, so the next reader cannot tell that the row is out of date. (build, #1343)
Wording narrower or looser than the behavior.
- One resolved
traces_toedge raised seven population tallies of theadoptionblock by one each, with no new finding. Among them arerelation.target.unresolved(886 to 887),relation.target.is_source,relation.target.suspect,relation.endpoint.not_permitted,lifecycle.dependency.on_initialandwarrant.evidence.unsupported. A tally under the name of a rule reads as a count of failures, and this one counts every edge the rule reads. No document says which it is. (build, #1386)
Paid, and struck from the list above. #1487 paid one of the six. The Discharge section of HW-OBL-0200 said that the seal removes every document under docs/ that names a selected probe. That sentence was narrower than tools/probe/seal.sh. It now names the probe shelves, .headwater/export.json and the answer keys. It also names the identifier claims and the lines that cite a removed document. It names each file outside docs/ that names a probe and is not a declared fold.
Five stay, and each one waits on a person. The two edges are created_by: agent, so a person types them. The stamp item needs a rule that nobody has ruled. The review row stays as written, because a review is a point-in-time record. #1487 looked for the document that describes the tallies of the adoption block and found none that says what a tally counts. So the tally item has no home to write the sentence into yet, and where it goes is a ruling too.
Discharge
Each item discharges alone, when the file it names says or does what the item asks, or when a change records why it stays. The record discharges when every item has. An item that grows a reader outside this repository leaves this record for an issue, and the record says where it went.