session 2026-09-10: the scoping sitting — REVIEWED-138/-139, the child-gate FIX, PENDING-182/-183, and six register defects

Session record, ledger, MEMORY.md rotation (prior Active Session demoted to
MEMORY-reference.md), OWED-6 queued against the frozen ladder, KG triples, and
skill-harvest proposal D.

N-now re-measured for REVIEWED-123 condition 2: 59, split 31 real / 28 mumble.
⚠ Not commensurable with the banked 36.9%, which used the one-prompt predicate.
The ladder pointer's 'direction has REVERSED / rising fast' clause is superseded
— it was a dated finding read as a status, and it contradicted the new figure in
the same sentence.

claude/memory/MEMORY.md

@@ -37,7 +37,7 @@ permalink: claude-memory/memory
 **Loud trigger — pointer suffices**
 - [Chamber work: ground in constitution + charter + runbook FIRST](feedback-chamber-work-ground-in-constitution-charter-runbook.md) — **any chamber work *or talk about it*** begins there (incl. `reanchor:`). Repo CLAUDE.mds are pointers, not state; corpus claims come from a self-tested tool, never a hand grep.
 - [Governance files are dotfiles symlinks](reference-governance-files-are-dotfiles-symlinks.md) — Edit/Write refuse to write through a symlink, so **edit the real `~/dotfiles/…` path** when appending — **`PENDING`/`REVIEWED` only.** ⚠ That refusal is a tool artifact, **not** a permission check, and this note is the documented route past the only friction guarding the constitution (PENDING-107). **`~/CLAUDE.md`/`~/REVIEWED.md`/L2 = `[ESCALATE]`, steward's hand — a jurist sign-off does not authorize one.**
-- [Verification ladder](reference-verification-ladder.md) — the named instruments; reach for the gate the claim's shape demands instead of re-deriving one. ⚠ **FROZEN — REVIEWED-123 (2026-08-17): no additions, rewordings, removals or reorderings, from ANY source, whatever its authorization**, until the trial is graded (N-now **65/84, measured 2026-09-03** — *and the direction has REVERSED: 52 on 08-31, 65 today, **rising fast and rising for the wrong reason**. Composition, measured the same day by the fool's own prompt signature: **41 real + 24 mumble (36.9%)**. The earlier reading here — 44/84, "DOWN 7 from 51", "shedding faster than it gains" — was **wrong in the number and backwards in the direction**; corrected 2026-09-03 as a record-only arithmetic fix (PENDING-179 gate 2b). The counter is still a 30-day ROLLING WINDOW per PENDING-147, so it can fall; it is not falling now. ⚠ **Report the COMPOSITION with the count** — a bare 65 reads as 65 sessions and roughly a third is machine chatter (PENDING-178). Re-measure, never relay: `len(glob('~/.claude/projects/-Users-davidglidden/*.jsonl'))`, the trial's own method at `governance-drift-check.py:513`*). Entries earned meanwhile queue in **PENDING-141's owed-entries list** (4 rows). Reading it is unaffected — that is the point of the freeze.
+- [Verification ladder](reference-verification-ladder.md) — the named instruments; reach for the gate the claim's shape demands instead of re-deriving one. ⚠ **FROZEN — REVIEWED-123 (2026-08-17): no additions, rewordings, removals or reorderings, from ANY source, whatever its authorization**, until the trial is graded (N-now **59/84, measured 2026-09-10** — split **31 real / 28 mumble**; ⚠ the 36.9% banked on 09-03 used the ONE-prompt predicate and is **NOT commensurable** with today's two-prompt split (OWED-6). The window fell 65→59 between 09-03 and 09-10, which a 30-day ROLLING WINDOW can do (PENDING-147) — ⚠ **the earlier note here claimed the direction had REVERSED and was rising; that reading is SUPERSEDED by today's measurement and was a dated finding read as a status.** ⚠ **Report the COMPOSITION with the count, and the PREDICATE with the composition** — a bare 59 reads as 59 sessions when nearly half is machine chatter (PENDING-178), and a composition compared across predicates is not a trend (OWED-6). Re-measure, never relay: `len(glob('~/.claude/projects/-Users-davidglidden/*.jsonl'))`, the trial's own method at `governance-drift-check.py:513`*). Entries earned meanwhile queue in **PENDING-141's owed-entries list** (4 rows). Reading it is unaffected — that is the point of the freeze.
 - [Skill-harvest register](skill-harvest-register.md) — canonical home for proposed skills (governed analog of PENDING.md for tooling); `/wrap-up` §1.6 proposes, steward authorizes. **Rebuilt 2026-08-07** from the archive: **154 live proposals**, grouped by kind, each with an exact `archive:L###` pointer. ⚠ The 2026-08-01 compaction was *lossless but illegible* (55 scraped header rows, 95% of cells cut mid-word) — the count it advertised, 177, was never the number. ⚠ **THE STROKE-2 BATCH IS AUTHORIZED BUT SHOULD NOT BE EXECUTED YET — PENDING-141.** 41 rows stamped `S2` are authorized (2026-07-19, execution not a ruling) and 22 are `S2?` (unsettled). **BUT appending them triples the ladder from 20 entries WHILE a pre-registered trial is measuring whether the ladder is reached** (baseline 14%, graded at 84 transcripts). Ladder size is an uncontrolled variable in that design, so executing the authorized batch would confound the only check behind REVIEWED-95's causal claim. **⚖ RULED — REVIEWED-123 (2026-08-17): AUTHORIZED (a) HOLD, on six conditions, and the freeze is GENERAL rather than S2-specific.** Grading does NOT authorize the append — the batch returns for a *ruling*. Report **N-now at every wake** until lifted; 30-day review is a live `DEFERRED-DECISION`. ⚠ Filing new proposals now requires a **declared firing moment** (`/wrap-up` §1.6); one that cannot name it is documentation and must say so.
 - [Copy-paste-clean governance drafts](feedback-governance-drafting-copy-paste-clean.md) — fenced, paste-ready blocks for **entries**; ⚠ **AMENDED 2026-09-10: a COMMAND for whitespace/line-anchored REPAIRS** (a fenced block is what adds the indentation), and **verify by exact-string check with a negative control — the 'by eye' clause is SUPERSEDED.** A `##` with two leading spaces renders perfectly and parses as nothing.
 - [Verify-before-compose hook](feedback-verify-before-compose-hook.md) — chamber constitutional writes are BLOCKED without `<!-- GROUNDED-IN: … -->` + verbatim Grounding. Don't fight the block.
@@ -75,35 +75,34 @@ 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 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.
+> 🔑 **THE REGISTER IS CHECKED ONLY WHEN A PARTY ELECTS TO CHECK IT.** Six defects in the
+> record in one evening — a broken title, a dropped table row, a heading indented two spaces,
+> two stale line citations in placed rulings, a count stated in two units. **Every one was
+> found because someone chose to run a check.** The worst — a ruling that renders perfectly
+> and is invisible to every `^##` reader — **could not have been found any other way.**
+> Nothing watches the register. The candidate instruments exist and none is authorized.
+> ✅ **DONE 2026-09-10 — the jurist's four-item brief, run in order and stopped where told.**
+> **REVIEWED-138** (count in BOTH units: **4 named instances / 7 occurrences — or 11 under a
+> per-control reading**; PENDING-180 discharged, ⚠ **structural remedy still open**) ·
+> **REVIEWED-139** (errata, two stale citations, recorded by joining) · `7948c09` **[FIX]**
+> the `Stop`-fires-for-`claude -p` gate, mutation-verified · **PENDING-182** three-field
+> counter **drafted, NOT ruled, FORM A already excluded** · **PENDING-183** eleven items named.
+> ⚠ **THREE TRANSIT MECHANISMS, ONLY TWO CATCHABLE BY READING** — wrap at ~150 cols · dropped
+> clause/row · **leading indentation, which renders correctly and parses as nothing.**
+> ⚠ **MY OWN BANKED RULE CAUSED ONE:** *"verify the draft parses as intended by eye"* — the
+> one instrument that cannot see it. **Superseded by joining** (fence for entries, **command
+> for whitespace repairs**, exact-string + negative control for both).
+> 📌 **JURIST: a SIXTH same-direction closure by the register's enumeration** (it self-reported
+> three, then **withdrew its count as recollection rather than defend it** — *one is evidence,
+> the other testimony about it*). Docketed at PENDING-89 with the population bound: **a rate
+> over the caught is not a rate over the misses.**
+> ⚠ **PENDING-139 option (a) SHIPPED 2026-08-31 under REVIEWED-132** while the item still reads
+> *Awaiting*; ⚑ flag is correct in mechanism, false in implication. **CLASS E mirrored.**
+> ⛔ **N-now = 59, split 31 real / 28 mumble, measured 2026-09-10** — ⚠ **NOT comparable to the
+> banked 36.9%**, which used the one-prompt predicate. 30-day review **2026-09-16**, joint
+> -178/-179 same date. **OWED-6 queued** (rule of three fired on the transcript classifier).
 
-- [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`.**
+- [Session 2026-09-10 — the scoping sitting](session-2026-09-10-the-scoping-sitting.md) — the four-item brief delivered and stopped on time; then the register failed at itself six times. **PULLING: the register is checked only by election — nothing watches it.** **FIRST MOVE: PENDING-182, FORM A already excluded; `tick_id`'s allocation site is the open design point.**
 
 ## 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).