session 2026-08-09 close: marking sheet built (92a97d0); index trimmed 21.0→19.7KB; harness read limit MEASURED at 24.4KB

claude/memory/MEMORY.md

@@ -6,7 +6,7 @@ metadata:
   type: note
   permalink: claude-memory/memory
   originSessionId: 22915403-bc5d-4796-9c7d-196b7c30d2f9
-  modified: 2026-08-09T19:42:11.754Z
+  modified: 2026-08-09T19:50:40.617Z
 permalink: claude-memory/memory
 ---
 
@@ -67,19 +67,18 @@ 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 "PRESERVED" FIXTURE WAS A 0-BYTE FILE.** `corpus/pattern-finder-station-i-pass1.md` — committed empty at `38de1a9` (2026-06-26), one commit, never written, **unreproducible**. Three documents carried *"do not delete or regenerate it"* for **seven weeks** and no currency pass ever opened it. Found by **checking the inherited question's premise before answering it**.
+> ⚠ **THE "PRESERVED" V4 FIXTURE WAS A 0-BYTE FILE** (`38de1a9`, 2026-06-26, never written, unreproducible). Three docs carried *"do not delete or regenerate it"* for **seven weeks**; no currency pass ever opened it. Found by **checking the inherited question's premise before answering it**.
-> 📋 **TOMORROW, steward-directed at the 2026-08-09 wrap: PROMOTE THE LINK-RESOLUTION CANARY TO A SCRIPT.** It is **already on the ladder AND named in a `/wake-up` step** — and was still typed **inline twice on the record** (2026-08-08; 2026-08-09's index rotation). ⚠ **The gap is neither knowledge nor home; it is that no home carries an EXECUTABLE**, so it is re-implemented at each firing — the banked *"re-writing what is already banked"* violation, and the K column's whole point. → `~/dotfiles/scripts/`, **invoked** by `/wake-up`, not described; cover `](file.md)` **and** `[[wikilink]]` across MEMORY.md + MEMORY-reference.md; distinguish pre-existing- from newly-broken; **carry a positive control** (a deliberately dead pointer) — an unexercised canary is the silent-net class.
+> 🔑 **PULLING THREAD — V2's ENGLISH GOLD: narrow the March anchors DIVISIONS → SPANS.** The ONE act unblocking three of P7's four findings (EN `taggable:false` · **29×** cell asymmetry · §7.3 negatives near-unconstructible). It is an **authoring act** ⇒ propose-and-mark-`unverified`; ⚠ do **NOT** shortlist with `retrieve.py`/`ground.py` — the instruments under test. **START: the Alexander eight**; Harrison's fourteen are ~350k chars, their own session.
-> 🔑 **PULLING THREAD — V2's ENGLISH GOLD: narrow the March anchors from DIVISIONS to SPANS.** The ONE act unblocking **three of P7's four findings** (EN `taggable:false` · the **29×** cell asymmetry · §7.3 negatives near-unconstructible in EN). ⚠ It is an **authoring act** → route is **propose-and-mark-`unverified`**; do **NOT** shortlist with `retrieve.py`/`ground.py`, which are the instruments under test. **START: the Alexander eight** (short); Harrison's fourteen are ~350k chars and their own session.
+> ⚠ **P7 ALREADY RAN (2026-08-07, `corpus/v2-stratum-tags.yaml`) — READ IT BEFORE DERIVING.** Asymmetry measured (EN divisions median 27,833 vs FR spans 969). Also: the **fr authoring plan inverts** — inherited 1A:9B, §6.3 lands ~1:27 vs §6.2's 1:1 ⇒ **~8 stratum-A pairs needed that nothing asks anyone to write.**
-> ⚠ **P7 ALREADY RAN (2026-08-07, `corpus/v2-stratum-tags.yaml`) — read it before deriving anything.** The "baseline asymmetry" is **measured**: EN divisions median **27,833** chars vs FR spans **969**. Also: the fr authoring plan **inverts** (inherited 1 A : 9 B; §6.3 would land ~1:27, not 1:1 — **~8 stratum-A pairs needed that nothing asks anyone to write**).
+> 📋 **TOMORROW (steward-directed): PROMOTE THE LINK-RESOLUTION CANARY TO A SCRIPT.** Already on the ladder AND in a `/wake-up` step, yet typed inline twice on the record (2026-08-08, 2026-08-09) — ⚠ **the gap is neither knowledge nor home but the absence of an EXECUTABLE.** → `~/dotfiles/scripts/`, **invoked** not described; `](file.md)` + `[[wikilink]]` over both memory indexes; pre-existing vs newly-broken; **carry a positive control.** ⚠ **EARNED 2026-08-09, before the script exists: STRIP INLINE CODE SPANS BEFORE MATCHING.** The inline version flagged one dead pointer — which was the link pattern *inside this very line's own specification*. Uncorrected, the canary flags its own documentation forever and the real signal drowns. With code spans excluded: **48 pointers, 0 dead.** (Third self-reference defect of the day, after the preservation header and the neutrality check.)
-> ✅ **REVIEWED-113 + 114 placed.** `pattern_finder` re-run **still PASS-BUT-FALSELY** — and **V0/V1 could never have changed it**: all 36 citations verbatim + correctly located, so V1 passes every one; the defect is **V3/V4's tier**. **Abstention 0/12**, beside N2's **0/5**. 129 built (`6f6bac5`) + the organ's first suite; fleet **8 suites / 263 checks**.
+> ✅ **REVIEWED-113 + 114 placed.** Re-run **still PASS-BUT-FALSELY** — **V0/V1 could never have changed it**: 36 verbatim, correctly-located citations ⇒ V1 passes all; the defect is **V3/V4's**. **Abstention 0/12** beside N2's **0/5**. 129 built (`6f6bac5`) + the organ's first suite; fleet **8 suites / 263 checks**.
-> ⚠ **My errors were all in CHECKS, not writes** — a round-trip that tripped on its own instruction · an induced-red that deleted the symbol (traceback, not a named failure) · an exit code read through a pipe. And **steward-caught: I twice wrote PENDING-130 was UNRULED.** *Ruled ≠ placed ≠ condition-discharged.*
+> 🔒 **STANDING CONDITION — REVIEWED-114 §3–4: NO DOCUMENT CALLS EITHER RE-RUN "V4's FIXTURE" AND V4 IS NOT BUILT UNTIL THE STEWARD'S DATED KEY EXISTS.** Item stays **OPEN**. ⚠ Ruled **(a)** — only the condition is outstanding; do not re-open it as a question. ✅ **Sheet BUILT and waiting**: `corpus/answer-key-2026-08-09-UNMARKED.md` (`92a97d0`) — 36 items, spans pulled from source (36/36 verified), **nothing pre-filled**; the steward is **judging, not confirming**. ⚠ Not blind: the executor stated a coarse per-primitive reading in conversation beforehand; a disclosure line was offered and **declined (2026-08-09)**.
-> 🔒 **STANDING CONDITION — REVIEWED-114 conditions 3–4 (placed 2026-08-09). NO DOCUMENT MAY CALL EITHER PRESERVED RE-RUN "V4's FIXTURE", AND V4 MAY NOT BE BUILT AGAINST ONE, UNTIL THE STEWARD'S DATED ANSWER KEY EXISTS.** The item stays **OPEN and unarchived** until then. ⚠ Ruled **(a)** — the artifact *is* to become the fixture; only the condition is outstanding, so do not re-open it as a question. The key is marked **against the corpus, not the report** (only a 320-char `_snip` per citation), and **only the steward is differently formed** — condition 6 forecloses delegating it to the jurist. The four documents **were** corrected (`20f8958`, no "fixture", no "retro-gated"); it is the *assertion* that is barred, not editing. Artifacts: `ec6fa0b` (pre-fix = REVIEWED-113's byte-identity control) · `8746dcf`+`07727dd` (post-fix candidate). **Retire this line only when the dated key exists.**
+> ⚠ **All my errors today were in CHECKS, not writes** — a round-trip that tripped on its own instruction · an induced-red that deleted the symbol (traceback, not a named failure) · an exit code read through a pipe · a neutrality check that matched its own legend. And **steward-caught: I twice wrote PENDING-130 was UNRULED** — *ruled ≠ placed ≠ condition-discharged.*
-
-- [Session 2026-08-09 — the fixture was an empty file](session-2026-08-09-the-fixture-was-an-empty-file.md) — **Checked the inherited question's premise before answering it, and the premise was false.** The re-run is **still PASS-BUT-FALSELY**, and V0/V1 could never have changed it (36 verbatim citations ⇒ V1 passes all; the defect is V3/V4's). **PENDING-129/130 filed, ruled and placed as REVIEWED-113/114**; 129 built (`6f6bac5`) with the organ's first suite — ⚠ and the ruling's own fourth cell turned out to be a **`KeyError` crash**, not the inferred silent collapse. Two artifacts preserved with three-part provenance; four documents corrected (`20f8958`). ⚠ **The placed record contradicted the relay for the third consecutive time.** **LITERAL Q: Mauss serves the Ranaipiri testimony and a Havámál strophe as citable Mauss with no `role: quotation` — two-source accident, or a class?**
 
+- [Session 2026-08-09 — the fixture was an empty file](session-2026-08-09-the-fixture-was-an-empty-file.md) — the day's full record: premise-check, PENDING-129/130 → REVIEWED-113/114, the `KeyError` that corrected its own ruling, two artifacts preserved with three-part provenance, four documents corrected (`20f8958`), and the marking sheet. ⚠ **The placed record contradicted the relay for the third consecutive time.** **LITERAL Q: Mauss serves the Ranaipiri testimony and a Havámál strophe as citable Mauss with no `role: quotation` — two-source accident, or a class?**
 ## 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).
 
 ## Index discipline (self-bounding — keep this file lean)
 Wake-loaded live index; hard budget well under the harness load ceiling. Keep to: Standing preferences · Canonical Trackers *as one-line pointers* (chronological detail lives in the linked tracker files, **not** here) · Active Session · these pointers. Rotation + budget-breach handling are wired into `/wrap-up` (demote prior Active Session on promote) and `/wake-up` (truncated load = flag + trim). Back up before restructuring.
-*Compaction history: 2026-07-17 re-slimmed to one-liners, 20.5→17.1 KB. 2026-08-07 trim (steward-directed): 19.9→~15 KB by the fires-silently/loud-trigger split, plus `project-studium-engine.md` created to hold engine state MEMORY.md had been carrying inline. **⚠ 17.1 KB is a prior achievement, not a derived ceiling** — the real harness load limit is unmeasured; if it ever matters, measure it rather than inheriting this number.*
+*Compaction history: 2026-07-17 re-slimmed to one-liners, 20.5→17.1 KB. 2026-08-07 trim (steward-directed): 19.9→~15 KB by the fires-silently/loud-trigger split, plus `project-studium-engine.md` created to hold engine state MEMORY.md had been carrying inline. **⚠ MEASURED 2026-08-09: the harness read limit is 24.4 KB** (surfaced by the index-size hook), which answers the standing "unmeasured" caveat this line used to carry. 17.1 KB remains a prior achievement, NOT the ceiling. 2026-08-09 trim: Active Session block condensed 5.2→3.6 KB, 21.0→19.4 KB total (80% of the real limit). ⚠ Going below ~18 KB requires restructuring **Standing preferences** (9.4 KB, the largest section and explicitly the fires-silently set) — a proper task, not an end-of-day squeeze.*

claude/memory/session-2026-08-09-the-fixture-was-an-empty-file.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: project
   originSessionId: d5f5c224-f249-41a3-87ce-cb2d50c6e1f4
-  modified: 2026-08-09T19:42:45.129Z
+  modified: 2026-08-09T19:48:54.055Z
 ---
 
 # Session 2026-08-09 — the fixture was an empty file
@@ -146,7 +146,11 @@ or from running the thing, never from my own review.
    alone (condition 3 + 6). Until it exists REVIEWED-114 stays OPEN, no document names a
    fixture, and V4 is not built. **SPLIT THE WORK — the executor half is unblocked and is
    step 4a:**
-   4a. EXECUTOR: build the marking sheet. For each of the 36 citations emit, in emission
+   4a. ✅ DONE 2026-08-09 (`92a97d0`, pushed) — `corpus/answer-key-2026-08-09-UNMARKED.md`,
+       generator kept at `scripts/build_answer_key.py`. 36 items, 36/36 file-pulls verified
+       byte-identical to the grounded JSON, 36 blank verdicts, emission order.
+       **Only 4b remains.** Original spec kept below as the record of what was asked for:
+   4a-spec. EXECUTOR: build the marking sheet. For each of the 36 citations emit, in emission
        order and with NO grouping or ordering by my judgment: the primitive statement · the
        locator (`work` §`section_id` L`a`–`b`, so the steward can always open the source) ·
        the FULL span text pulled from the corpus (not the 320-char `_snip`) · a blank verdict