PENDING.md had 112 unclosed headers, 56 of which a placed ruling names. They were
invisible as closed to a human reading the file, which is what made the file
unopenable — 926 KB. Not a correctness change: the closure rule already read them
correctly after this morning's [FIX]. This is so the register can be opened.
Done under the archive's own rule from the 2026-07-28 split — "archive only on
explicit evidence of closure — a matching REVIEWED-N" — so this continues that
operation rather than inventing a policy. Headers and numbering unchanged, entries
not edited.
VERIFIED PER-ITEM AGAINST REVIEWED.md, NOT AGAINST THE CLOSURE RULE. That rule was
widened hours earlier and was the thing under test; moving 56 items on its say-so
would have made it the authority for its own correctness. 56/56 matched a ruling
header directly, 0 held for want of one.
NINE HELD BACK, and this is the part that is not mechanical. Every PENDING-131 and
PENDING-142 block stays. A ruling names an ID; it does not dispose of a BLOCK filed
after it (PENDING-145), and the decidable unit is the block, not the id
(PENDING-146). Both items are open and both state that live asks sit under those two
ids — PENDING-131 ADDENDA 2 and 4 "await steward action now", and PENDING-142
ADDENDUM 3 names a jurist ruling still awaiting placement. Archiving them would have
buried exactly what those two items exist to make visible. A date-based test caught
only one of the nine; the register's own testimony caught the rest.
Moved in four tranches, each re-reading both files from disk. Readback: 47/47 present
in the archive, 0 remaining in PENDING.md. Conservation against the pre-move backup:
131 headers before, 84 + 47 after, 0 lost, 0 duplicated. PENDING.md 926 KB -> 528 KB.
Both instruments re-run: wake-digest 99 controls, drift-check 59/59, queue still 56.
One defect introduced and fixed before commit: the tranche banner was written as a
`## ` header, which under this system's own rule makes it an item. Demoted to prose;
archive parses at exactly 121.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
8abfe88's message read "PENDING.md split 1848→430 + archive", but the archive was
never staged: that commit deleted 1,532 lines from PENDING.md and pushed the
deletion without its destination. The 74 closed governance items survived on disk
and in history only — recoverable, but absent from the record the remote carries.
The commit claimed an integrity it had not enacted.
Verified before committing, not after: every line of
PENDING.md.bak-2026-07-28-pre-split is accounted for in
(PENDING.md UNION PENDING-archive.md) at line granularity — no regex, no parser
notion of "item" — with a same-run positive control (a sentinel absent from the
union must be reported missing) per the Q2 epistemic standard. Three baseline
lines are absent by intent, all in the file header: the stale `Repo: bmf` and
`Branch: fix/replay-durability-contracts` pointers (that branch merged as
c9746ae; HEAD is main — the staleness was flagged in PENDING-78), and the
`Protocol:` line, reflowed. That header rewrite rode along inside 8abfe88
unmentioned; it is logged here rather than left silent.
Second fix, same class: the header asserted "the next item is PENDING-80" while
79, 80, and 81 all exist. Replaced the stated number with the rule that computes
it — a number goes stale, a rule does not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
