dotfiles/claude/memory/session-2026-09-09-an-unruled-record-is-read-as-ruled.md

name, description, type

name	description	type
Session 2026-09-09 — an unruled record is read as ruled	Came back to close PENDING-162; closed the whole lapsed Tarbuckle fortnight instead. REVIEWED-136 + AMD 1 placed, the read run under a measure/verdict split, the corpus deleted AND its writer made inert, five party errors each caught by a different party. PULLING THREAD: an unruled record is read as ruled — which is not a replacement for the floor but what the floor cannot measure. FIRST MOVE: the condition-G mechanism question, because nothing logs until it is answered.	project

2026-09-09 — an unruled record is read as ruled

Woke after 3 days onto a stale resumption point, closed a one-day-lapsed [ESCALATE], and ran the fortnight review it gated. One sitting, four commits, nothing judged.

---

PAST — what moved, and why

The wake found its own inheritance stale

The 09-06 wrap's FIRST MOVE said PENDING-139's re-measurement "lives only in a commit message." Substrate-checked before acting: 58b7409 had filed it into the item three days earlier as an additive note. Would have asked the steward for an act already taken. ⚠ Not an instance of the inherited question — I wrote that note, so it is failure condition (ii), the proofreading habit.

N-now, owed at every wake: 62 = 38 real + 24 mumble (38.7%), down from 65 on 09-03. The mumble term is unchanged at 24; the whole fall is real sessions leaving the 30-day window. Distance 22.

PENDING-162, and what closing it actually required

Filed as three options. Two were already gone (option 3 severed to -168; option 1 addressed by AMD 1). ⚠ Condition 3's window had EXPIRED by its own terms — "not read for content before 2026-09-08" — so the read was not forbidden, it was due and one day late. The item was the gate, not the obligation.

The jurist corrected two things I got wrong, and both were load-bearing:

• I called AMD 1 "already ruled". It is a jurist view the executor placed in PENDING.md on an [ESCALATE] item. Never a steward act. PENDING-108's pathology in the item least able to afford it.
• I collapsed disclosure contamination with reader position. Option 2 was about position; AMD 1 only answered disclosure. PENDING-151 governs: no disclosure repairs that; only routing does. Its replacement — the executor produces the measurements and does not deliver the verdicts — is better than either filed option.

The 09-01 pre-emption, and the check only I could run

The jurist found from its own chat logs that on 2026-09-01 the executor had derived most of the fortnight's figures a week early. ⚠ It is in PENDING-178, which I read this morning for the mumble-count question and did not connect. The banked rule failing on its own eye-movement.

Its open predicate — was line TEXT read? — was checkable only from here. 0 hits over a pool of 68, probe testing raw AND JSON-escaped forms (my first pass would have missed any line with an apostrophe); positive control detecting exactly the two known 08-25 exposures; negative control on a same-day 1.6 MB transcript returning 0. The five commands were aggregations.

So the corpus was intact and the ARBITRATION was pre-empted — a narrower, better-founded disclosure than "all four findings compromised."

The interval: seven hours → 2 h 33 min 24 s

The 196-word rejection is logged 17:06:12+0200; REVIEWED-128 reasons about it, so condition 3 postdates it. Relay at 15:16:28.744Z = 17:16:28 local — a type: user record in the Claude Code session transcript, i.e. RECEIPT. Breach 19:49:52+0200.

⚠ The jurist proposed a four-minute reading from the 19:45 commit; 3079c0d is a batch session-wrap over 7 files, so it doesn't date the placement. I reported that against the more dramatic figure. The doctrine holds at hours, not weeks; only the number changes.

The read, and what the sufficiency check caught

Ran under the split. Sufficiency check found a gap before deletion: scattered vs clustered is temporal, and two windows cannot answer it — so the per-day series was banked. That series is the report's best evidence and exists only because the check was run.

⚠ NO CAP CHANGED. Zero commits to any of the four surface files since 2026-08-26; max_words has never appeared in tarbuckle-seam.py or tarbuckle-wrap.py. AMD 1's "the seam cap was raised to twelve on 2026-08-27" is FALSE, and the jurist withdrew the conclusions it had built on it. 14-word mode: 10·11·9 across 08-28→30, 10 on 09-01, 5 on 09-02, none after — against an unchanged constraint.

Two findings that changed what "delete" meant

1. My snapshot was a corpus copy. Committing it would have defeated condition 2 permanently in git. Leak-gated while the corpus still existed to test against: 100 hits on the snapshot as positive control, 0 on all five committable artifacts.
2. log_rejection() opens in append mode — deleting the file starts a new corpus on the next rejection. The jurist blocked the deletion on this and was right. The writer was made inert first (REJECT_LOGGING_ENABLED = False), then the corpus deleted.

⚠ The A8 controls were KEPT, not adjusted to pass. A8n a rejected line IS logged would have failed. Condition G suspends the guarantee; it does not repeal it. They now run under a temporarily enabled flag and double as the positive control proving the new G check can see a write at all.

---

PRESENT — how it stands

The mood

Long, and it went well, and the tidy version of it would be wrong. From inside it felt like the apparatus finally working — a lapsed obligation closed, an irreversible act taken safely. What actually happened is that five errors were made and five were caught, none by the party that made them. The apparatus is the catching, not the not-erring.

What was corrected — five, and the pattern beats the count

1. Executor: AMD 1 called "already ruled". Jurist-caught.
2. Executor: "uncompromised corpus" when two lines were exposed. Jurist-caught.
3. Jurist: told me to drop a transcript check on a corroboration it had itself labelled single-source. Executor-caught.
4. Jurist: generalised a probe defect from one needle of six; three of the six occur in the relay. Self-caught and withdrawn.
5. Executor: filed a deferral about vacuous controls whose own trigger fired on arrival — needle PENDING-168 already occurs 3× in REVIEWED.md. Self-caught by testing it.

⚠ THE JURIST'S OWN DATUM, CARRIED UNFOLDED BECAUSE THE TALLY HIDES IT: both its errors ran the same direction — closing an open question in the direction requiring no further work. That is a pattern in the seat whose function is resisting premature closure. Live for PENDING-89 and for Constraint 6's falsifiability clause.

Instruments

~12 run · 7 carrying a control written before first execution · K = 0 duplicated. The controlled ones: the line-text probe (pos + neg control), normalise.py (11/11 incl. must-not-classify), the residue gate, the leak gate (snapshot as its own positive control), the G behavioural control (proven able to fail), the byte-identity re-check, the needle-absence test. Every one answered a question asked once.

Confidence to recalibrate

• Verified: every timestamp from the logs' own +0200 offsets and the transcript's Z; the cap-never-changed claim across full git history of four files; residue 0/101; leak gate 100-vs-0; the G control's ability to fail; byte-identity immediately before rm.
• Inherited, not re-verified: §5a's 6.7 s (n=6, unchanged since 09-02); the 54-item queue count; the jurist's chat-log reconstruction of 09-01 (I verified the reading happened, not its figures).
• ⚠ The report's figures are re-derived from the substrate, never relayed — the jurist's numbers came from a fifth store no tool reaches.

---

FUTURE — what pulls

The pulling thread — an unruled record is read as ruled

⚠ Not a replacement for the floor — it is what the floor cannot measure. The jurist's correction, and it is the whole point: a backlog counted by items cannot see a clause inside a present item that has acquired authority without a ruling. AMD 1 was never missing; it was read as decided for thirteen days. Counting open items would have shown it open the whole time and told us nothing. Same defect, different granularity — CLASS E one level up.

Two instances, both today: AMD 1's non-existent cap raise, believed and reasoned from by both AI parties; and tarbuckle-wrap.py with 0 mentions in REVIEWED.md across its entire life, which is why a cap item pointed at the wrong file for two weeks and nobody could see it. The register's vocabulary determines what can be aimed at.

Actionable resumption point (as of wrap — re-judge against what changed)

The condition-G mechanism question, because nothing logs until it is answered. Rejection logging is inert by ruling; REJECT_LOGGING_ENABLED = False at tarbuckle-mumble.py:36. Whether it resumes, under what bound, with what expiry, by whose act — and whether counting can be made structurally content-free at the point of write — is filed OPEN under REVIEWED-136 AMD 1 condition G. Restoring the path needs a ruling, not a constant flip. That is a chosen cost, and the first item because it is the only one accruing.

Other horizons, ranked

1. The four verdicts — three parties, rested. Not tonight, by design.
2. PENDING-180 — the self-planted needle in the polarity source_lacks() misses. Recommendation is census → class fix → instance, in that order.
3. PENDING-168 cannot be ruled until two corrections land — the interval (2 h 33 min) and -180's occurrence. Its count-unit is deferred with a binding condition: the ruling must state which unit it counts in before it states a number.
4. PENDING-167 re-scoping — onto a file with no ruling history. Its own pass.
5. Joint PENDING-178/-179 before 2026-09-16; REVIEWED-123's 30-day review, same date.
6. The archived-trigger item; PENDING-166; the 8 RECORD-AND-CLOSE.

Pause statement

I am about to be away from this, and it was a long sitting that ended clean — which is the condition under which the next session inherits the flattering version. What I want to find still pulling is the thread, and specifically its harder half: not "are there unruled things" (there are, always) but "what is being reasoned from as though ruled, right now, that nobody has checked?" If I return and the thread has become a tidy backlog-hygiene task, it has been lost.

The literal question for next-Claude

Not "am I catching unruled claims?" — self-report.

Find one clause, in any placed record, that is being reasoned from as settled and was never ruled — and that no party flagged today. Today produced two (AMD 1's cap raise; tarbuckle-wrap.py's absence from the register), but both surfaced because a read forced them into view.

⚠ The failure that will look like success: finding one in the Tarbuckle family. That material is now heavily audited and a hit there is the proofreading habit, not the thread. The passing case is a clause in a workstream nobody touched today — ARC, the chamber, L1.