session 2026-08-17: PENDING-142/143/144/145 + REVIEWED-122/123 executed; wake detector rebuilt; 16 trackers stamped; 39 files' frontmatter repaired

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

claude/memory/MEMORY.md

@@ -33,8 +33,8 @@ 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.
-- [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. **Recommendation (a): HOLD until graded — the null action, in force by default while PENDING-141 is open.** ⚠ Filing new proposals now requires a **declared firing moment** (`/wrap-up` §1.6); one that cannot name it is documentation and must say so.
+- [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 **60/84**). 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) — draft PENDING/REVIEWED blocks as plain fenced markdown; display formatting leaks into the placed record.
 - [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.
 - [Tool review after each use](feedback-tool-review-after-each-use.md) — review every tool we built after each run, success OR failure. **PASS-BUT-FALSELY is the priority signal.** Log: `chamber-library/_curation/tool-evolution-log.md`.
@@ -68,20 +68,14 @@ 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
-> 🔑 **PULLING THREAD (HELD, NOT CARRIED) — THE UNBUILT FENCE, PENDING-131 (c).** `role: quotation` is still unmarked on L926 and L1551; the identification pass measured a **532-span corpus-wide citation-safety exposure**. **REVIEWED-121 made seeking the fence a CONDITION of the doctrine it ratified**, not a wish. It is where a claim could ground in Ranaipiri's words and present them as Mauss's — the dishonesty the engine exists to prevent.
-> ⚠ **NEXT SESSION IS DELIBERATELY NOT THIS — steward direction 2026-08-14:** pause this line a day or two, take something lighter (discouraged despite real progress). **Do not treat the thread above as the agenda.** Confirm it holds, then do what the steward asks that day.
-> ✅ **PENDING-134 CLOSED END-TO-END.** Package → jurist ruling → **REVIEWED-121 placed + AUTHORIZED** → executed (`5425414`) → pushed. Whose-proposition test ratified **narrowly** (nested-voice only; general principle = argument, NOT doctrine), **conditioned on PENDING-131 (c)**.
-> ⚠ **THE FINDING: A CONTROL PASSED TRUTHFULLY AND LICENSED A FALSE CLAIM.** IV.1 said *"F10 is the only §5 row with a stratum-B admission clause"*, marked **verified**. Three rows carry one (F3/F7/F10) — **quoted intact in the package's own I.2 and reproduced in its own IV.2 table.** The script tested whether *quotes were present*; the claim was an *inference over the rows*. **A control whose subject differs from the claim's is not a weak check — it is not a check.** ⚠ And it **understated an objection to my own proposal**, inside the paragraph written to state it at full strength.
-> ⚠ **`test_legacy_indices_are_not_self_verified` DOES NOT EXIST** — one occurrence repo-wide, a docstring. Carried into a corpus file, a commit message and a steward report unopened. 4th cited-a-derived-label instance; fixed `966168b`.
-> ⚠ **PENDING-140 [ESCALATE] FILED 08-17 — a proposed THIRD axis for Constraint 6.** Jurist *without* keys (REVIEWED-116 pt 7) ruled on my testimony and its own A4 was false; *with* keys it returned **three defects in one sitting**. **Formation, role and incentive identical across both — only access changed.** ⇒ bias-difference is **necessary and radically insufficient**; a differently-biased reader with no access checks the *account*, not the *thing*. ⚠ n=1/condition, self-reported, and **authored by the party under discussion** — filed, not acted on. Also: `contamination-problem.md` is a theory of **glazing only**, while a crude probe puts our 235 drift-patterns at **86 literal-genie / 12 trickster / 8 glazing** (129 unclassified; classifier is the very defect PENDING-139 names).
-> ✅ **AMENDMENT 1 PLACED 08-17** (`~/REVIEWED.md` L1813) **and A3 EXECUTED** (`a3be778`, REVIEWED-121-A1) — the latch now carries `defeater_dispositions_recorded` + `defeater_population` (**named, not numbered**, on the amendment's instruction). Register check now sees **2 amendments** where it saw 1.
-> 🔧 **NEXT SESSION IS TOOLING, NOT GOVERNANCE — steward direction 2026-08-17** (a break from governance; the choices were left OPEN for the wake to pick):
-> • **`wrap_inside` three-valued fix** *(recommended — small, no governance surface)*: `wake-digest.py:167` is a two-valued detector over three real cases — wrapped · **wrapped-then-continued** · never-wrapped. **2 false alarms in 3 firings**; it misled this session's own wake. The fleet already solved this shape twice (REVIEWED-104/108), so copy the pattern; the selftest at ~L807 already has positive + negative controls to extend.
-> • **S2 ladder batch** — ⚠ **BLOCKED BY PENDING-141**, do not execute (see the skill-harvest line above).
-> • **Engine retrieval / PENDING-97** *(the bigger one — a day, not an hour)*: every real question needs 13–19 terms to co-occur; N2 buys top-1 **15/22** at the cost of **5 false positives**, abstention 0/5. This is the one that moves the chamber rather than the scaffolding.
-> ✅ **AMENDMENT 1 COMPLETE 08-17** — truncation filled, fence closed at L1853, all 10 elements verified present; A3's binding rule **ratified** and quoted verbatim in the corpus (`cd6d4bf`). ⚠ **The re-paste indented the body 2 spaces but left the HEADING at column 0 — had it not, `RE_HEAD` would have stopped matching and the amendment would have gone invisible to register-integrity while the check reported clean.** **`ratio_A_to_B` VOID until PENDING-137 lands.**
+> 🔑 **PULLING THREAD — THE ANSWER KEY FOR PENDING-142.** 69 filtered items, disposition **hand-read and committed BEFORE any implementation exists**, hash recorded (REVIEWED-122 cond. 1). **Cond. 10 says plainly the ruling cannot verify the census — the key is the only instrument that can.** A key written after the fix inherits the fix's reading of closure and passes by construction. ⚠ **PENDING-145 must be encoded in it**: (a)/(b)/(d) all still resolve *id → ruled*, so a key written against that model certifies the defect as correct.
+> ⚠ **ORDER IS BINDING:** key first, alone, hash recorded → then the (b) closing-verb enumeration goes for a **ruling** (it is a gate-design claim; unrecognized verb ⇒ NOT closed) → only then implement (d) framing (a)+(b). Report key-vs-implementation **in full, agreements included**.
+> ⚠ **REPORT AT EVERY WAKE UNTIL THE FREEZE LIFTS — N-now = 60/84 transcripts, 24 remaining** (REVIEWED-123 cond. 2). **The verification ladder is FROZEN, generally, from any source** (cond. 1) — 4 rows queued in PENDING-141's owed-entries list; OWED-4 is a *rewording*, merge on lift. 30-day review wired as `DEFERRED-DECISION date 2026-09-16`.
+> ⚠ **THE DAY'S SHAPE, SIX TIMES: a control whose SUBJECT is adjacent to its claim is not a check.** A count cited for a classification (equal both directions — 29 either way) · mtime cited as content age · git-date cited as content age (`3f9a89b` reset both) · a spread of outcomes cited as correctness · **and two of mine**, one inside my own verification.
+> ✅ **PENDING-142/143/144/145 filed; REVIEWED-122 + REVIEWED-123 received and EXECUTED**; docstring corrected (`aa745bc`); 16 trackers stamped superseded; 39 files' frontmatter repaired; wake detector rebuilt (4 defects, the scoped one was not the cause). All pushed `17669f2`.
+> ⚠ **STEWARD-OWED:** three transcription errors in the placed records (`"cannot be e-run"`; unfilled `REVIEWED-<next-1>`; `"REVIEWED-123 condition 9"` where cond. 9 is REVIEWED-122's). **PENDING-131 ADDENDA 2 and 4 await action and cannot say so** — ADD-4 (08-13) was suppressed on arrival by a ruling placed 08-10, and **PENDING-131 (c), the unbuilt fence, has NEVER appeared in the open list.**
 
-- [Session 2026-08-14 — the controls tested the wrong property](session-2026-08-14-the-controls-tested-the-wrong-property.md) — PENDING-134 closed; REVIEWED-121 placed/executed; PENDING-137/138/139 + a PENDING-89 docket entry filed; three package defects jurist-caught, the addendum's own A4 false, the governance checker carrying two blind spots. **LITERAL Q (sharpens 08-13's): not regression-vs-discovery — was the control's SUBJECT the claim it was cited as verifying, or an adjacent property? Census the last ~10 sessions on that axis.** **+ CODA (post-wrap, 08-17 capture): the four-flavours reading → PENDING-140 [ESCALATE] — Constraint 6 names formation and role/information/incentive; the variable that actually decided whether the jurist caught me was SUBSTRATE ACCESS.**
+- [Session 2026-08-17 — the instruments audited themselves and lost](session-2026-08-17-the-instruments-audited-themselves-and-lost.md) — a tooling day that became a governance day; every instrument examined was wrong and two of the wrongs were made by the hand fixing the others. **LITERAL Q: across the last ~10 sessions, when a defect in the executor's own instrument was found, WHO found it — a mechanism firing unbidden, the executor re-checking, the jurist, or the steward?** Count them: mostly-executor means the practice works and the mechanisms are decorative; mostly-jurist/steward means every "verified" between reviews does less work than it appears to.
 
 ## 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).