session 2026-09-09 night: REVIEWED-137 verdicts sitting + PENDING-180 [FIX] executed

Session record, ledger merge, Tarbuckle tracker entry, 7 KG triples.
Pulling thread: the unit of the measurement is not the unit of the claim.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BsN7nKHjKBsn5bfNRRCNmo

claude/memory/MEMORY.md

@@ -74,30 +74,35 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.
 
 ## Active Session
-> 🔑 **AN UNRULED RECORD IS READ AS RULED — and this is NOT a replacement for the floor, it is what
-> the floor cannot measure.** 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**. Same defect, different granularity — CLASS E one level up.
-> **The register's vocabulary determines what can be aimed at.**
-> ✅ **DONE 2026-09-09:** REVIEWED-136 + AMD 1 placed (`71226a4`) — PENDING-162 CLOSED, option 2
-> replaced by **executor measures / jurist+steward judge** · the lapsed fortnight read run under
-> that split · corpus deleted **and its writer made inert** (`3d45e3a`) · PENDING-180 filed
-> (`5635763`) · two fired deferrals discharged (`98bbf60`).
-> ⚠ **NOTHING IS JUDGED.** The four verdicts are reserved to a rested three-party sitting.
-> ⛔ **NOTHING LOGS until condition G is answered** — `REJECT_LOGGING_ENABLED = False` at
-> `tarbuckle-mumble.py:36`. Restoring the write path needs a **ruling, not a constant flip**. This
-> is the FIRST horizon because it is the only one accruing.
-> 📌 **FIVE party errors, each caught by a different party.** ⚠ **Both jurist errors ran the same
-> direction — closing an open question in the direction requiring no further work**, in the seat
-> whose function is resisting exactly that. Carried unfolded because "five errors, five catchers"
-> hides it. Live for PENDING-89 and Constraint 6's falsifiability clause.
-> ⚠ **PENDING-168 cannot be ruled** until two corrections land: the interval (**2 h 33 min 24 s**,
-> not seven hours) and PENDING-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.
-> ⛔ **N-now owed at every wake with its split: 62 = 38 real + 24 mumble (38.7%)**, down from 65.
-> Distance 22. 30-day review **2026-09-16**, joint -178/-179 same date.
+> 🔑 **THE UNIT OF THE MEASUREMENT IS NOT THE UNIT OF THE CLAIM.** A number produced over one
+> population, read as answering a question about another, with **nothing in the record marking the
+> substitution**. Three substrates in one sitting: the **rejection timestamp** (child-completion,
+> read as tick time — this killed judgment 2); **my own verification predicates, 3×** (per-line
+> where the unit was per-paragraph; per-file where it was per-entry); and **PENDING-168's count**,
+> whose unit is formally deferred. The register names the governance case (CLASS E) and has **no
+> name for the measurement case**. Yesterday's thread was authority-without-a-ruling; this is the
+> layer beneath.
+> ✅ **DONE 2026-09-09 night — REVIEWED-137 placed (`3d340f6`)**, the four PENDING-169 §5 judgments.
+> **Presence ANSWERED** (occupied on a per-machine clock, occupancy uncorrelated with the work).
+> **Fidelity retrospective UNANSWERABLE** · **condition-G instrument DESIGNED, NOT AUTHORIZED** ·
+> **wrap cost answered, wrap cap UNANSWERABLE**. Plus `049ca57` `[FIX]` + `e611bee` addendum.
+> 🔥 **THE FINDING THAT DISPLACED THE QUESTION: the 14-word pile-up and the tick→terminal lag are
+> ONE phenomenon** — 44 of 50 pile-up-day rejections unattributable vs 1 of 52 elsewhere, **no
+> exceptions either direction over 14 days**. So **every cap argument rests on a confounded base**,
+> the attended split is VOID, and **08-31 kills the W1/W2 framing — it toggles.** Mechanism UNKNOWN.
+> ⚠ **`log_rejection` timestamps at write time**, so the **banked per-day series is binned by
+> child-completion** on exactly the five days that matter — and the corpus that could check it is gone.
+> ⛔ **CONDITION G STILL STANDS.** `REJECT_LOGGING_ENABLED = False`, re-verified unchanged at
+> `3d45e3a`. **`tick_id` is the field to add — named by two failures, not designed.**
+> 📌 **JURIST: THREE closures in the direction requiring no further work**, the third *inside the
+> sitting where the executor flagged the first two*. Live for PENDING-89 + Constraint 6.
+> ⚠ **The repaired self-planting mechanism is NOT whole** — `source_has`/`source_lacks` cover the
+> **assertion**, not the file; **prose can plant the needle** (I did it, in the comment explaining
+> the bug). REVIEWED-137 §6 declares it verified.
+> ⛔ **N-now owed at every wake with its split** — re-measure, never relay. 30-day review **2026-09-16**,
+> joint -178/-179 same date.
 
-- [Session 2026-09-09 — an unruled record is read as ruled](session-2026-09-09-an-unruled-record-is-read-as-ruled.md) — came back to close PENDING-162; closed the whole lapsed Tarbuckle fortnight instead. The 09-01 pre-emption found **in an item I had read that morning** · the line-text probe (0/68, pos+neg controls) · the interval falsified 7 h → **2 h 33 min** · **no cap ever changed** (AMD 1's raise never happened) · the snapshot caught as a corpus copy before commit · the writer stopped before the file. **PULLING: an unruled record is read as ruled.** **FIRST MOVE: the condition-G mechanism question.**
+- [Session 2026-09-09 night — the unit of the measurement](session-2026-09-09-night-the-unit-of-the-measurement.md) — the verdicts sitting. Four judgments, **two answered and two recorded UNANSWERABLE with reasons — the more valuable half**. Presence: per-machine clock, idle panes take the draws, **tick starvation leaves no trace**. `0 of 89 into mumbles` was **FALSE and I certified it structural** — `Stop` fires for `claude -p`. Then the steward released PENDING-180's fix: census found **exactly one** self-planted needle, `source_has` built, mutation-verified — **and I re-planted the bug in the comment explaining it.** **PULLING: the unit of the measurement is not the unit of the claim.** **FIRST MOVE: draft the item list from the carry list in `01. Daily/2026-09-09.md`.**
 
 ## Historical reference → MEMORY-reference.md
 Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1).