Wrap amended after it was written, because the thread moved.
PENDING-146 filed at steward direction: the open list's unit is the id, the
decidable unit is the ## block. Upstream of everything PENDING-142 reaches, and
worse than a wrong verdict because the verdict is right.
Corrects my own report to the steward: FOUR blocks under PENDING-131 carry a live
Awaiting (parent, ADD-1, ADD-2, ADD-4), not the two I named. The jurist ruled on
that testimony while explicitly disclosing it had not verified ADDENDUM 1; running
that one check overturned the count. The disclosure was the instrument — no
control was pointed at it.
The answer key's specification changed before the key was drafted: it must be
keyed on ## BLOCKS, not ids, recording per block whether a live Awaiting exists
and at what tag. Keyed on ids it would have reproduced the unit that caused Class
E and graded green.
Resumption point revised and superseding the wrap's: three live options, steward
stopped tired without picking. (A) Move 2, closable in one sitting, no ruling,
and it is the fence itself. (C) Move 1, the emission-side fence over all 532
spans. (B) the answer key, session-sized. Recommendation absent a preference:
(A) then (C).
KG +3: the census-of-what-I-looked-at drift pattern; the disclosed-scope-limit
prevention; and the unit-of-a-pre-registration catch.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4
Session record, ledger, index rotation and KG appends for the day the
instruments were audited and lost.
Filed: PENDING-142 (open/closed criterion answers an adjacent question) with
three addenda, PENDING-143 (carrier restoring PENDING-121 by hand), PENDING-144
(script-resident substrate claims are checked by nothing), PENDING-145 (a ruling
claims a NUMBER, not a record — PENDING-131's addenda suppressed on arrival, and
the unbuilt fence has never appeared in the open list).
Executed: REVIEWED-122 conds. 6/7/9-as-amended/11 and REVIEWED-123 conds. 1/2/3.
N-now recorded at 60/84 transcripts. Ladder frozen generally; 4 rows queued in
PENDING-141's owed-entries list, two of them earned today (mtime-is-not-content-age;
verify a bulk edit against the pre-change state from git). OWED-4 flagged as a
REWORDING to merge on lift rather than append beside.
Index rotated: prior Active Session demoted verbatim to MEMORY-reference.md,
new one promoted. MEMORY.md 20,242 bytes (83% of the 24.4 KB read limit) —
under budget but the restructuring task remains owed.
KG: 7 lines — 4 drift-patterns, 3 preventions, including the DEGRADED banner
catching its own author's regression and a confound filed against the executor's
own favourable evidence.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4
The record is updated where information ARRIVES and never where a reader LOOKS.
Three instances found the same day, each with the correct information already
written down elsewhere:
REVIEWED-81 (AUTHORIZED 07-28) -> PENDING-81 still reads open
the ARC open-work register, which -> those 6 trackers still read live
says in its own description that
it supersedes them, with a
per-file verified verdict
register entry A2: "the content -> register entry B3, one page below:
half (B3) is now unblocked + "[OPEN - gated on A2]"
started" (06-17)
The third is the sharpest: both halves sit in the SAME document, so no tooling
gap explains it. ~/CLAUDE.md already rules this under Memory Discipline
("mark the superseded record as superseded"); the rule is being applied to facts
and not to trackers, PENDING items or register entries, which are also facts
about state.
Executed under steward authorization, arrears only:
- 16 trackers stamped `superseded_by:` + `superseded_on:` AND a visible in-body
banner. The banner is the point — metadata alone repeats the defect, since the
finding is about what a reader sees. 9 obsoleted by the 2026-07-07 MemPalace
wind-down; 7 already carrying the register's own verified `DONE-retire`.
- B3's label corrected, with the two-month error left visible rather than
silently amended.
- Nothing moved, renamed or deleted: 381 pointers resolve, 0 dead, 0 mis-authored.
HARVESTED BEFORE STAMPING, and this is why the harvest came first:
`project-mempalace-library-incremental-remine-strategy` carried a steward-verbatim
rule that is instrument-independent — never run a single multi-day index; order by
criticality; gate each tranche on READBACK, not on write-success (933,576 drawers
once stored successfully and could not be read back at all). It lived only inside
a MemPalace tracker, so retiring the instrument would have retired the rule with
it. ~/CLAUDE.md names that exact hazard: "state the obligation first and the
instrument second, or the next retired tool takes a rule down with it." Now
`feedback-bulk-indexing-runs-incrementally-with-readback.md`, and it applies to
studium-engine corpus work.
Held back deliberately: 2 correctly-parked files with named dependencies, 2 named
nowhere (returned to the steward), and 39 trackers unread — recorded as a gap,
not as a finding.
Measurement note: every earlier estimate of tracker staleness was wrong, because
both mtime and git-last-commit were reset across 283 files by the 2026-06-06
normalization sweep. The honest figure excludes it: median 90 days.
Filed as PENDING-142 ADDENDUM 2 per steward direction (fold, do not file anew).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4
Filed from Task 1 of the 2026-08-17 jurist relay. `governance_state()` computes
openness from one signal — whether a REVIEWED header names the PENDING id — and
never reads the item's `Awaiting:` field, any status field, or the ruling's
`Decision:`. Six items are misclassified in both directions:
- 3 falsely OPEN (78, 81, 82): rulings that name the title, not the id. All
AUTHORIZED 2026-07-28. REVIEWED-78's own Notes record that it was filed as a
separate entry precisely to satisfy the closure rule as it then stood; the rule
later changed, breaking the entries written to comply with it.
- 3 suppressed under a design gate rather than a steward authorization, one of
which (PENDING-121) is marked HELD OPEN by its own ruling.
- 2 structurally unclosable: no `PENDING-N` in the header, so no ruling can ever
close them. One is the ICP-19 item gating Observer Problem work.
- 39 suppressed items still carry a live-reading `Awaiting:` line.
Removing the false opens and restoring the false closures leaves 29 — the number
the tool reports. The change proof standing behind the current implementation
measured exactly that count (18 to 19). A count-based control cannot see a
classification wrong in both directions by equal amounts: its subject was the
population size, the claim's subject was each item's disposition.
Addendum 1 flags that the selftest asserts the defect as intended behaviour,
with one of the three hidden items as its fixture.
Nothing patched — the relay scoped this to findings only.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4
