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-reference.md

@@ -17,6 +17,23 @@ metadata:
 
 # MEMORY — Reference layer (consult on demand)
 
+<!-- demoted from MEMORY.md at the 2026-08-17 wrap -->
+## 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.**
+
+- [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.**
+
 ## Relocated from MEMORY.md at the 2026-07-19 evening budget trim (verbatim; wake-value judged low — MemPalace-era mechanics + reactive-mode ARC specifics)
 
 - [Session 2026-08-03 — the governors that never engaged](session-2026-08-03-the-governors-that-never-engaged.md) — the inherited question answered, and it became the day's theme: **controls that exist in code and never engage**, invisible because an inert control reports success. **Census 01** (pre-registered): `fool/` strong, but **drift-check 3-of-5 families INERT** and **71 of 75 ladder entries cited nowhere** (no IDs ⇒ firing history unrecordable). **S-series closed** on discovering the **jurist ruled all Q1–Q5 on 2026-05-18** and the items were mislabelled 2½ months (S6/S7/S9 built · S2 rebuilt as `[FIX]` · S4/S5 withdrawn with MemPalace). Dormant legacy + GH swept: **22 → 10 open**; `#170` found **undelivered since April**. Steward lifted the L1 baton rule → **mindfabric-00 pinned 6 days**; CDP profile named it; **`ANALYZE` never run in 4 months** so SQLite preferred a *boolean* index over the selective one (**6.4×**, 99.8%→6.0%, `/health` silent→200 in 0.13 s). **B1.1's cap verified WORKING ⇒ the defect is DATA, not code** — 836k edges minted before the governors landed; the ingest was **divergent, not slow**. **`coherence_evaluated = 0` of 813,178 — not one, ever.** ⚠ **Its headline claim was corrected 2026-08-04**: `ANALYZE` explained the *slowness*, not why the ingest never completes — see [[session-2026-08-04-the-replay-had-never-resumed]]. *(Demoted on promote at the 2026-08-04 wrap.)*