Rendered from docs/decisions/0106-a-governing-document-repoints-a-link-to-a-rule-that-moved-and-a-record-of-a-moment-stays-as-written.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

106 — A governing document repoints a link to a rule that moved, and a record of a moment stays as written

Context

A rule sometimes moves from one document to another. In #1572, the trim of spec 6 moved the export rules to spec 7. It moved the audit readings to the headwater taxonomy contract. It moved what a run states beside its findings to Checks and cache. Seven sections of spec 6 now state only a pointer to the new home. The adjudication of the slice counted links on 2026-10-03. Then 221 links outside docs/reviews/ and docs/probe-results/ still named spec 6. Of these, 96 were in evaluations and probe runs, and 125 were in 64 documents that still govern.

Each link credits spec 6 for a sentence. Where the rule moved, the credit is now one hop from the text that states it. The question was which of the two classes of document to change. An evaluation records what was true when someone measured it, and a change to it rewrites history. A decision or an obligation that is still in force tells a reader where the rule is today.

The owner ruled twice on 2026-10-03, in the decisions file of run 20261002-1233:

OWNER (2026-10-03) #1572-dated: the owner said 'review and repoint the decision if it hasn't been superceded, leave the evaluation as it was (assuming it notes the git sha it was evaluated at). This seems like it should be a general rule unless I am missing something?' The adjudicator for slice 4 checks the decision is not superseded and repoints it, and checks the evaluation names the commit it was evaluated at before leaving it. Whether this is a general rule is for the product owner to answer from the corpus at its next pass.

OWNER (2026-10-03) #dated-records: the owner chose 'Yes, short decision record': a document that still governs (an accepted decision nothing replaced, an obligation, a spec, a guide) has a link to a moved rule changed to the new home with no change to what it claims; a record of a moment (an evaluation, a review, a probe run) stays as written, and its date stands for the moment when it names no commit. It is written as a short decision record, and the last slice of the spec 6 trim (#1572 slice 4b) applies it.

The second ruling replaces the commit condition of the first. An evaluation that names no commit stays as written, and its date marks its moment.

Decision

A document that still governs changes a link to a moved rule to the new home of the rule, and it changes no claim. These documents govern:

  • a decision at current that nothing supersedes,
  • an obligation at any status, which includes a discharged one,
  • a specification part, a subsystem spec and an interface contract,
  • a guide (a how-to or a tutorial), the glossary and a README.

A record of a moment stays as written. These are records of a moment: an evaluation on either shelf, a review, a probe run, a probe result, and a superseded decision. Where the record names a commit, the commit marks its moment. Where it names none, its date marks its moment.

A sentence that reports what another document said is history, and it stays. A governing document that writes "spec 6 said" in the past tense describes an earlier text, and that earlier text did say it.

A new link keeps the claim of its sentence. Where the sentence quotes words, the quotation marks stay only if the new home holds those words. Where the home states the rule in other words, the author keeps the claim and the link, and the pull request lists the case. Nothing is dropped without a record.

A link to a section that still states the credited rule stays. A pointer section of spec 6 still places each rule in the engine. A sentence that credits spec 6 for that placement keeps its link.

A sentence whose claim stopped being true when its rule moved is corrected in place. This applies to a present-tense sentence in a governing document that credits the old home with a rule that only the new home states. The author repoints the sentence to the new home and changes its claim until the new home holds it. The author adds no dated note. The rule above keeps a claim that the new home still holds, and this rule covers a claim that it does not hold. The owner ruled this for clause 9 of #1572 on 2026-10-03:

OWNER (2026-10-03) #1572-clause9: "Repoint and correct in place". Each present-tense sentence in HW-DR-0029 (lines 31 and 78), HW-DR-0043 (line 30) and HW-DR-0033 (line 33) that credits spec 6 with a rule it no longer states is repointed to the new home and its claim corrected in place, as a documents-only slice. Supersedes the product owner's recommended dated-note option.

Consequences

  • The governing links to the seven pointer sections of spec 6 now go to the homes. engine/crates/cli/tests/spec_six_inbound_links.rs fails on a governing document that links one of the seven again. It skips the records of a moment by path, and it skips a document at status: superseded. Its allow table holds the links whose sentence credits spec 6 for the placement that the pointer section still states. A second table holds the 34 links that the evaluations keep to the seven sections, so a repoint inside an evaluation also fails.
  • A second test in the same file reads credits in prose. A sentence names spec 6 by a link, with or without an anchor, or by the plain words. The test reads each such sentence that puts a present-tense verb after the name. The verbs are a closed list of seventeen, such as "says", "puts" or "keeps". Up to two words of a relative clause ("which", "that", "where it") and then up to two adverbs may come between the name and the verb. After a possessive name, up to three words of a noun may come first. A sentence that opens its claim with "according to" and the name is also read. A verb is not a credit when a negator follows it at once, as in "holds no" or "states nothing". The same is true when a negator ends its clause, as in "names it nowhere". The test reads such a sentence as a statement of what spec 6 does not hold, and that reading is usually true. It fails when that sentence or the next one holds a term of its table of moved rules. A third test fails when spec 6 holds one of those terms again, or when the home of a term does not hold the rule. On 2026-10-03 the second test found thirteen such lines, and each was corrected in place under the rule above. Ten were in seven decisions, one was in the graph-build subsystem spec, one was in HW-OBL-0143, and one was in the engine README.
  • The tests cannot read five kinds of credit. The first is a credit whose wording no row of the table names. The second is a credit whose verb is not on the list. The third is a credit in a shape that the test does not read, such as a verb after a longer clause. A reader checks those, against the rules above, and adds a row, a verb or a shape for each one found.
  • The fourth kind is a credit to a moved rule that is itself negative. An example is "Spec 6 says no generated file states when it was generated". The fifth kind is a credit whose clause ends in a negator. An example is "Spec 6 says a placeholder sits there and an aggregate entry does not". The negator rule above reads each of the two as a statement of what spec 6 does not hold, so neither one fails. On 2026-10-03 no governing sentence had either shape. The ruling on the third verify of #1572 kept the negator rule and listed these two misses. The rule opens again when a governing sentence of either shape appears in the corpus.
  • The test can also flag a sentence that is true. A term anywhere in the credit sentence or the next one is a hit. So a correct pointer fails when it names a moved term beside a credit to spec 6. The writer then words the sentence so that the term does not sit beside the credit.
  • An evaluation, a review or a probe run is never edited to follow a moved rule. A reader who follows its link to an older home reads a pointer there, and the pointer names the new home.
  • "Names its commit" is not yet a fact that a check can read. #1652 carries that work, and it carries this rule into the shipped package, because an adopter meets the same choice when a rule moves.
  • HW-DR-0078 is the nearest earlier ruling. It lets a recording keep a frozen number when a recorded-on date stands beside it. This record applies the same idea to a link. A date or a commit marks a moment, and the record of that moment does not follow the corpus.