session 2026-09-09: REVIEWED-136 + AMD 1, the Tarbuckle fortnight read, PENDING-180, and the session record

The lapsed 2026-09-08 obligation, closed. Session memory, ledger, KG (7 lines),
skill-harvest proposals A and B, and the demote-on-promote of the 09-06 Active
Session block into MEMORY-reference.md.

Pulling thread: an unruled record is read as ruled — which is not a replacement
for the floor but what the floor cannot measure.

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

claude/memory/MEMORY.md

@@ -74,36 +74,30 @@ 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
-> 🟡 **THE COUNT IS NOW MEASURED, AND A MEASURED COUNT HAS TO BE MAINTAINED.** Do not inherit
-> *"the backlog dissolved"* — it did not. **The number had no referent.** 114 unclosed headers / 64
-> after the closure filter / **54** once two readers stopped miscounting / 43 once four rows are seen
-> as two items. All defensible. The 64 carried for weeks was an artefact of which reader was asked.
-> ⚠ **54 will drift the same way 64 did.** It is a maintained figure now, not a fact.
-> ✅ **DONE 2026-09-04/06:** REVIEWED-134 (grading suspended, terminus 2026-10-15 with its own
-> trigger) · REVIEWED-135 + AMENDMENT 1 (fr pass, three stale records corrected) · two reader
-> `[FIX]`es, each enumerated before landing with the negative control that would have caught it
-> during its life · 47 items archived, **9 held back** because live asks sat under ruled ids.
-> 🔑 **THE WEEK'S YIELD, STATED SMALL BECAUSE THE ARC AROUND IT WAS WRITTEN TOO KINDLY** (jurist,
-> 2026-09-06): two reader fixes, three corrected records, one disclosure that no longer overstates
-> itself. **None of it came from ruling well** — it came from finding the number had no referent.
-> Of five stale-record instances, **two were the jurist's**, written into governance records before
-> anyone caught them. A tidy ending is the condition under which the next session inherits the wrong
-> lesson.
-> 📌 **CARRY FORWARD, in this order:** (1) [[feedback-a-dated-measurement-is-not-a-status]] — and the
-> half that does the work is **read the whole block, not the field you came for**; (2) PENDING-140's
-> third axis is **reach PLUS a forced check**, and both instances were **self-imposed falsifiers** —
-> a condition written by the party it then caught; (3) **every condition that worked this week named
-> something ANSWERABLE rather than something to consider.** The rest is administration.
-> ⛔ **N-now is owed at every wake WITH its real/mumble split** (REVIEWED-134 cond. 5; 30-day review
-> **2026-09-16** stands). At suspension: **65 = 41 real + 24 mumble (36.9%)**, distance 19.
-> ⚠ **`ratio_A_to_B` is VOID, AVAILABLE and UNSPENT — a ONE-SHOT, steward's act alone (REVIEWED-135
-> cond. 5). Ground is the best it has had: blind replication, live positive control. DO NOT SPEND IT
-> ON MOMENTUM.** The fr cell is one act from closing.
-> 📌 **STEWARD OWES:** PENDING-162 (**2026-09-08**) · joint -178/-179 **before 09-16** · the 8
-> RECORD-AND-CLOSE · **the floor** · PENDING-139 **re-measure before ruling — leg (A) is REPAIRED,
-> leg (B) live** · the `~/_Dev/claude-transcript-archive` git-init · PENDING-171 · -160 · -168.
+> 🔑 **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.
 
-- [Session 2026-09-04→06 — the count had no referent](session-2026-09-06-the-count-had-no-referent.md) — three days, one session: REVIEWED-134 applied · the 64-item triage (**45/8/8/3**, UNCLEAR only 3) · two reader `[FIX]`es on the SAME header shape in two instruments · 47 archived / **9 held** · REVIEWED-135 + AMD 1 · **the fr cell CLOSED and the one-shot spent**. ⚠ **Five stale-record failures of one class, two of them the jurist's** — banked as [[feedback-a-dated-measurement-is-not-a-status]]. **PULLING: the floor.** **FIRST MOVE: PENDING-139's re-measurement lives only in a commit message.**
+- [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.**
 
 ## 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).