Version: v0.1
Date: 2026-08-24
Status: Correction note. Sits beside cr-2026-234-human-authority-check-resolves-the-actor-v0_3.md; that document is not edited.
Corrects: change-requests/cr-2026-234-human-authority-check-resolves-the-actor-v0_3.md, H1 title line.
The document's H1 reads:
> # CR-2026-234 — The Human-Authority Check Resolves the Actor — v0.2
Its Version: field, two lines below, reads v0.3. The filename is ...-v0_3.md, and the footer line reads v0.3.
The Version: field is correct. The document is v0.3. The H1 is a carry-over from v0.2, which the draft was written over.
Record-doc versioning: a committed document is superseded by a next version, never edited in place. A one-character fix to the H1 would be an in-place edit of a filed document, and the discipline does not carve out an exception for small or obviously-correct corrections — the point of the rule is that it does not require a judgement about which edits are safe.
So the mistake stays where it was made and the correction sits next to it. A reader who reaches the v0.3 document and sees v0.2 in its title finds this note in the same directory.
The title line only. Everything else in v0.3 — the version field, the filename, the footer, the changes-from-v0.2 summary, §3b's either-space rule, §3b-i, §7b's correction, §7d's 2a results — is correct as filed and is what the executed work followed.
No content is affected. This is a label, not a claim: nothing in the document's substance depends on the H1, and no decision was taken on the strength of it.
Noticed by CC on reading v0.3 for execution, reported at the filing, and left uncorrected on instruction not to edit the filed document. The Operator has since ruled that the Version: field governs and that the correction belongs beside.
DUNIN7 — Done In Seven LLC — Miami, Florida Correction — CR-2026-234 v0.3 title line — v0.1 — 2026-08-24