Both 2026-09-08 triggers were discharged by today's sitting and would otherwise
have reported COME DUE at every wake forever, which is alarm decay by construction.
Each `resolved:` names what discharged it, per the schema's own rule that non-empty
is not enough. The four VERDICTS are explicitly NOT discharged by the report.
The classification deferral filed with PENDING-180 fired the instant it was written:
its needle was the bare string "PENDING-168", which already occurs three times in
REVIEWED.md from REVIEWED-136's own text. A vacuous trigger, committed inside the
item reporting vacuous controls. Corrected to the em-dash ruling-header form,
verified absent at filing rather than assumed — which is the check the first one
skipped.
The needle's limitation is disclosed in the block rather than left to be found: the
register writes ruling headers in at least four forms (80 em-dash, 3 parenthetical,
1 joint, 1 slash), text-present takes one needle and cannot be OR-ed, so silence
from this trigger is weak evidence and not proof.
Drift check: 6 deferred decisions tracked, none due, 4 resolved and kept.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbXpZup4GGCbLBbRJ79KpM
The dated steward act REVIEWED-132 §6 reserves for normalising a placed record. All
three Awaiting lines were false and had been for weeks; nothing in them turned on when
the dispositioning pass ran.
PENDING-133 (parent) — read "Steward authorization" for four weeks while its own
Status line, FOUR LINES BELOW ITS HEADER, recorded withdrawal by the proposer on
2026-08-10. Every reader showed a withdrawn proposal as awaiting the steward, and on
2026-09-05 it came within one act of being authorized as such.
PENDING-133 AMENDMENT 1 — discharged by REVIEWED-135 and its AMENDMENT 1.
PENDING-134 — ruled by REVIEWED-121, H3 disclosure placed at studium-engine 9221dd8.
H1's condition was satisfied by REVIEWED-117 and the record never said so.
⚠ A CONFLICT IN THE AUTHORIZING TEXT, RECORDED IN THE RECORD RATHER THAN RESOLVED
SILENTLY. Condition 6 directs PENDING-134's line to name "the ruling that disposes of
it" and defers the id to condition 7; condition 7 was discharged as REVIEWED-121,
verified twice. AMENDMENT 1 point 6 instead restates it as `REVIEWED-116 point 5` —
the authorization for the identification pass, quoted verbatim 44 lines above it in
the same document, and not a disposition of PENDING-134. Written as REVIEWED-121 on
condition 6's operative words and condition 7's verified discharge; the discrepancy is
annotated at the line and reported to steward and jurist.
PENDING-134's entry sits in an append-only archive whose header says "do not edit
entries". This edit is made under a dated steward act, the stated exception, and says
so at the line.
Effect: the visible queue falls 56 -> 54, both PENDING-133 blocks detected by the
Awaiting-line closure anchor added yesterday. Instruments green: wake-digest 99
controls, drift-check 59/59, no new register-integrity finding from the placement.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
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
