session 2026-08-06 evening: the parse fix landed + REVIEWED-87..94 placed + PENDING-108..111 filed

Governance: the register could not answer 'how many rulings do I owe' (23, not the digest's 26). Seven decisions that existed only in a narrative are now placed, five of them reconstructions carrying provenance lines. PENDING-99/-105/-106 closed (106 by split). PENDING-108/-109/-110/-111 filed. Engine: retrieve.py accepts a sentence (27b79ca). 26 crashes -> 0, MISLOCATED 0, FALSE-POSITIVE 0, HIT 0/22 — the engine now grounds nothing honestly, and 0/22 is recorded as the number to beat. PENDING-111 + jurist package: fidelity_equivalence@3 erases Alexander's invariant rating, found by the steward reading his printed copy. Relayed for ruling. Next session step 0, steward-directed: the MEMORY.md trim (19.9 KB vs <17.1 KB target; relocation not deletion), then N1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AB3Kryoy6b1pm2Nz1DYdLh
2026-08-06 22:28:53 +02:00
parent 3dff1a93d9
commit 02a72d017e
5 changed files with 116 additions and 4 deletions
@@ -36,6 +36,13 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index
 # Archived sessions + stable reference layer (relocated verbatim from MEMORY.md, 2026-07-06)
 ## Archived (2026-08-06 — the note that said it could not happen; demoted on promote at the 2026-08-06 evening wrap)
 > ⛔ **NEXT = the chamber PARSE FIX — decided jointly with the steward at the 2026-08-06 wrap, not defaulted into.** Make `engine/retrieve.py` accept a sentence; 26 of 27 real questions currently **crash**. Bounded, and it carries its own regression test (27 audited queries with known answers). ⚠ **Inherited constraint, load-bearing: the fix must NOT make the engine answer more.** Every obvious fix (strip punctuation, tokenize, add semantics) trades **loud failure** for plausible-but-wrong — the incident's exact behaviour. Read `studium-engine/docs/chavruta-retrieval-measurement-2026-08-06.md` §2 and §4 **first**: PENDING-97's filed description of the bug is wrong (you never reach conjunction; the query dies at parse).
 > ⏳ **Not my thread — do not confuse waiting with working:** the **Seb package** (agreed: when it can be done well; no external clock — three measured L1 write-path findings are ready for it) · the **L2 design note** (*every constitutional bound ships with a demonstrated negative instance, or it is documentation*) — wants dwelling, deliberately not composed fast. **REVIEWED-87 still drafted-not-placed** while `engine/fidelity.py:12` cites it as ratified. Q4 census + PENDING-104 brief need **dates, not "later."**
 - [Session 2026-08-06 — the note that said it could not happen](session-2026-08-06-the-note-that-said-it-could-not-happen.md) — **Both constitutional items CLOSED, not filed.** Constraint #1 reworded **by the steward's hand** after the executor **declined a jurist authorization it did not hold** — the tested case, and it held. The 08-04 "BMF stays down" decision **had not held**: the tracker's *"⚠ No KeepAlive"* note is **inverted** (plist unchanged since 03-07: `KeepAlive{SuccessfulExit:false}`+`RunAtLoad:true`) — **a crash restarts it; only a clean stop leaves it down** — so the 08-04 kill resurrected it, and **the false note is why nobody re-checked for two days.** Now `bootout`+`disable`d, both agents; prompt tax 3.11→0.22 s. **Chavruta measured: 26/27 real questions CRASH, 0 empties**; prediction pre-registered, **graded wrong on mechanism**. Three L1 write-path findings ready for Seb. **Steward reframed the incident pass — he wanted the design transfer, not a repo audit.** ⚠ Five same-class executor errors, three caught only by the steward.
 ## Archived (2026-08-05 evening — the brief contained the failure it commissioned; demoted on promote at the 2026-08-06 wrap)
 - [Session 2026-08-05 evening — the brief contained the failure it commissioned](session-2026-08-05-evening-the-brief-contained-the-failure-it-commissioned.md) — PENDING-101 run read-only: **two of its three framing findings die against the primary source; finding (2) holds** — a documented "never" relied on as a control, invisible until it failed. Jurist **and** executor independently hardened the same hedges → PENDING-102. **PENDING-107 is the largest: Constraint #1 says "cannot" and no mechanism makes it true.** Also 103–106; containment 17/17; five instrument-failures, two of which would have favoured the thesis under test. ⚠ **CORRECTED 2026-08-06:** that session's claim that the hook *"structurally cannot fire"* is false — it **fires on every `Write`/`Edit` and declines by design**, and `Bash` is not gated at all. Constraint #1's wording was fixed by the steward's hand 2026-08-06.
@@ -61,16 +61,19 @@ permalink: claude-memory/memory
 - [Source library — link + dedupe](project-source-library-link-and-dedupe.md) — steward's master ebook library = `~/Documents/___The Library [ePub_AWZ3]/` (2190 ebooks, messy nested). GOAL: link chamber↔sources (provenance index) + dedupe; real link needs EPUB/PDF internal metadata + edition-identity, not filenames. Detail + seed in file.
 - [Character-as-image hazard](feedback-character-as-image-hazard.md) — EPUBs rendering diacritics as inline images are SILENTLY MUTILATED by image-drop. Mechanism built (`apply_char_glyphs.py`, REVIEWED-70/v2.5.0), wired as a born-digital precondition; per-source glyph-maps still owed. VIEW the glyph; map to SOURCE form.
 - [Sidecar typology — protocol-dependent reading-indexes](project-sidecar-typology-protocol-dependent.md) — TWO layers: `.meta.json` structural sidecar = PROTOCOL-NEUTRAL (the graduated bar); reading-indexes (rich YAML) = PROTOCOL-DEPENDENT, probably PLURAL — **don't design the schema yet**; settle corpus to gold, let protocols declare themselves. Steward 2026-06-29.
- Studium Engine — *no tracker file yet*; moves in per-session memories + the **[architectural charter](reference-studium-engine-architectural-charter.md)** + **`docs/tool-evolution-log.md`** (built 2026-08-04 — organ reviews; **read its §0**: the discipline is attached to the human, so an automatically-invoked organ leaves no entry). Steps 0–7 built; corpus CLEAN; **V1 `verify-quote` + `fidelity_equivalence@3` GOVERNING** (ratified 2026-08-05, REVIEWED-87 — @2/@1 frozen; @3 = @2 + markup-delimiter exclusion, on ENGINE grounds + functional analogy, **NOT** chamber alignment. Greek/Latin census still owed and is a SEPARATE bump). ⚠ **Quoted tier accepts 6/17 of real human citation** (was 3/17) — the residual is elision/truncation/nested-quotes, not corpus defects; PENDING-99. ⚠ **The consuming end was first exercised 2026-08-04 and does not answer**: bare FTS tokens are conjunctive, no semantic layer, no test on `retrieve.py` at all (**PENDING-97**; silence now discloses its blindness, **PENDING-96** landed-but-open). Stage-1 rebuild plan: V1 done → V2→V4 / N1→N3.
+- Studium Engine — *no tracker file yet*; moves in per-session memories + the **[architectural charter](reference-studium-engine-architectural-charter.md)** + **`docs/tool-evolution-log.md`** (read its §0). Steps 0–7 built; corpus CLEAN + gate-validated 13/13. **V1 `verify-quote` + `fidelity_equivalence@3` GOVERNING** (REVIEWED-87 now PLACED) — ⚠ **but @3 is under challenge: PENDING-111 + jurist package filed 08-06**, it strips escaped literal `\*` and erases Alexander's invariant rating; ruling sets the V-track course. **The parse fix LANDED `27b79ca`** — `retrieve.py` accepts a sentence; 26 crashes → 0; **HIT 0/22, MISLOCATED 0, FALSE-POSITIVE 0**; `tests/test_retrieve.py` (21) + `tests/chavruta_harness.py` are the read side's first test floor. **PENDING-97 is now the live blocker and measurable** (13–19 term conjunctions). ⚡ **Embeddings already score 22/22 recall@20 on the same items** — never landed; V2 gates it. **NEXT: N1 → V2.**
 - [Instrument censuses — have our gates ever fired?](../governance/fool/census-02-have-they-ever-fired-RESULT.md) — `~/dotfiles/claude/governance/fool/`: **census 01** (does each gate have a real negative instance? → decay, not construction, is the failure mode) + **census 02** (has it ever fired at all? → the record divides by whether a human invokes it). Both pre-registered before the look; both had prediction 5 invert. Read before trusting any gate's silence.
 - [L1 reliability](project-L1-reliability.md) — canonical L1 tracker. **BLOCKED ON SEB (PENDING-94) — nothing moves until he rules; BMF is down and staying down.** The replay **has never resumed, only restarted**: `minCursor` is a minimum over all 11 modules and two never participate ⇒ every start rebuilds from seq 0 (13/13, 0 catch-up). Completion is gated by **uninterrupted run length, not rate** — which is why ANALYZE/B1.1/N6 were all real and all changed nothing. **Recall never worked either** (`retrieval_count = 0` across the whole April–June graph). Yesterday's "ingest mystery solved" was **corrected 2026-08-04**. **Read the tracker before ANY L1 work** — walked past once on 2026-08-03.
 - [Be (laundromat)](project-be-laundromat.md) — canonical Be tracker (est. 2026-06-08). Be = Skemantix startup (Seb+David) funding CapableMind's ladder; **bridge, not venture**. Decisions LOCKED (entity/pricing/infra in file); a11y gate MERGED. **Pre-revenue WTP gate = renovate Pat → charge her; discipline: no new spec until it clears → nothing for executor on be.** Repo @ `f43a0fd`.
 ## Active Session
-> ⛔ **NEXT = the chamber PARSE FIX — decided jointly with the steward at the 2026-08-06 wrap, not defaulted into.** Make `engine/retrieve.py` accept a sentence; 26 of 27 real questions currently **crash**. Bounded, and it carries its own regression test (27 audited queries with known answers). ⚠ **Inherited constraint, load-bearing: the fix must NOT make the engine answer more.** Every obvious fix (strip punctuation, tokenize, add semantics) trades **loud failure** for plausible-but-wrong — the incident's exact behaviour. Read `studium-engine/docs/chavruta-retrieval-measurement-2026-08-06.md` §2 and §4 **first**: PENDING-97's filed description of the bug is wrong (you never reach conjunction; the query dies at parse).
+> 🧹 **STEP 0 = the MEMORY.md trim — steward-directed at the 2026-08-06 evening wrap.** 19.9 KB vs a <17.1 KB target. **Relocation, not deletion**; back up first. Weight is Standing preferences (~9.6 KB) + Trackers (~6.9 KB) — judgement work, *not* a fast pass (fast trimming IS the compression-drops-the-load-bearing-clause failure). No truncation risk today (4.8 KB headroom); the reason it goes first is that it has been deferred three times.
-> ⏳ **Not my thread — do not confuse waiting with working:** the **Seb package** (agreed: when it can be done well; no external clock — three measured L1 write-path findings are ready for it) · the **L2 design note** (*every constitutional bound ships with a demonstrated negative instance, or it is documentation*) — wants dwelling, deliberately not composed fast. **REVIEWED-87 still drafted-not-placed** while `engine/fidelity.py:12` cites it as ratified. Q4 census + PENDING-104 brief need **dates, not "later."**
+> ⛔ **THEN N1, the navigation-tree builder** (decided with the steward at the 2026-08-06 evening wrap; then **V2**). The N0 contract is written and names all four primitives — read `studium-engine/docs/spec/n0-navigation-tree-contract.md` §1–§2, don't re-derive.
 > ⚠ **N1 will NOT move 0/22** — that is N2. Finishing N1 with the number unchanged is the expected outcome, not a failure.
 > ⚠ **Build the tree from the READING INDEX, not by parsing headings.** `chamber-library/reading-indices/*.yaml` carries the authoritative number→name→line map (Alexander: all 253, re-found *by name*, sha-bound). Heading text hits three documented OCR defects. Today's harness regex is a reference, not the input.
 > ⏳ **Not my thread:** the **PENDING-111 ruling** (relayed 08-06 evening — sets the V-track course, does **not** gate N1) · the Seb package · the L2 design note · PENDING-109 census + PENDING-104 brief, both **needing dates, not "later."**
- [Session 2026-08-06 — the note that said it could not happen](session-2026-08-06-the-note-that-said-it-could-not-happen.md) — **Both constitutional items CLOSED, not filed.** Constraint #1 reworded **by the steward's hand** after the executor **declined a jurist authorization it did not hold** — the tested case, and it held. The 08-04 "BMF stays down" decision **had not held**: the tracker's *"⚠ No KeepAlive"* note is **inverted** (plist unchanged since 03-07: `KeepAlive{SuccessfulExit:false}`+`RunAtLoad:true`) — **a crash restarts it; only a clean stop leaves it down** — so the 08-04 kill resurrected it, and **the false note is why nobody re-checked for two days.** Now `bootout`+`disable`d, both agents; prompt tax 3.11→0.22 s. **Chavruta measured: 26/27 real questions CRASH, 0 empties**; prediction pre-registered, **graded wrong on mechanism**. Three L1 write-path findings ready for Seb. **Steward reframed the incident pass — he wanted the design transfer, not a repo audit.** ⚠ Five same-class executor errors, three caught only by the steward.
+- [Session 2026-08-06 evening — the asterisk that carried meaning](session-2026-08-06-evening-the-asterisk-that-carried-meaning.md) — **The parse fix LANDED (`27b79ca`): 26 crashes → 0, MISLOCATED 0, FALSE-POSITIVE 0** across all 5 items where silence is the correct answer — both deciding buckets empty, so the revert condition was not met. **HIT 0/22**: the engine now grounds nothing *honestly*, needing 13–19 terms to co-occur. **0/22 is the number to beat.** ⚡ **The embedding arm already scores 22/22 recall@20 on the identical items** — capability measured in June, never landed; V2 is the gate that makes surfacing it safe. **Governance: the register could not answer "how many rulings do I owe"** (23, not the digest's 26) — REVIEWED-87→94 placed, five of them **reconstructions** with provenance lines; PENDING-99/-105/-106 closed (106 **by split**); PENDING-108/-109/-110/-111 filed. ⚡ **The steward's printed A Pattern Language found that `fidelity_equivalence@3` erases Alexander's invariant rating** (81/114/54 across the corpus) — jurist package filed, containment 13/13. **Instruments caught 4 corrections; the jurist 1; the steward 2 — and his came from reading a physical book.**
 ## 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; the MemPalace `handoffs` glance was retired 2026-07-07 with the wind-down).
@@ -579,3 +579,13 @@
 {"subject": "the never-delete-on-failure rule in the drainer", "predicate": "prevention", "object": "A data-safety rule produced a DIAGNOSTIC finding it was not written for. Built so a failed POST never unlinks a queued observation, plus a halt after 10 consecutive failures. On the first full run it self-stopped at 50/10,535 \u2014 and that halt is HOW the entity-pipeline finding surfaced (relationships=31556ms against a 30s budget, cursor held). A safety valve doubled as an instrument.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
 {"subject": "BMF (bettermemories, localhost:3011)", "predicate": "operational-state", "object": "STOPPED AND DISABLED 2026-08-06 16:47 \u2014 launchctl bootout + disable on BOTH com.capablemind.bettermemories AND com.capablemind.bmf (the latter carries unconditional KeepAlive:true and would fight for port 3011 if loaded). disable persists across reboot, closing the RunAtLoad door the 08-04 kill left open. Verified: port closed, no agents loaded. Plists backed up, NOT edited. Revert: bmf-stop-and-keep-stopped.sh --revert. 10,485 observations preserved at ~/.capablemind/hook-queue-parked-2026-08-06 \u2014 do NOT resume draining until the entity pipeline is healthy.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
 {"subject": "BMF (bettermemories, localhost:3011)", "predicate": "operational-state", "object": "down and staying down (2026-08-04 decision)", "valid_from": "2026-08-04", "valid_to": "2026-08-06", "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "READ-A-DATE-OUT-OF-AN-EXTERNAL-IDENTIFIER-AND-ANCHORED-OUR-TIMELINE-TO-IT. Wrote 'reconstructed eight days later' three times; INC-2026-07-28-01 is the UK AI Security Institute's INCIDENT id, not our filing date. Actual: same day. Jurist-caught. The correction made the finding WORSE (one day sufficed to lose four things permanently), which is the tell that the wrong number was doing argumentative work.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "MEASURED-THE-ARTIFACT-CORRECTLY-AND-MISREAD-WHAT-IT-WAS-FOR. Steward-named 2026-08-06. Counted 253 Alexander patterns accurately, then read a USAGE note ('32 selected patterns') as a bibliographic claim about extent. Same shape as asserting a fleet-wide causal story from n=5 and as '3 bare headings' when the count was 33. The measurement is right; the purpose-reading is wrong.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "ASSERTED-A-CONSEQUENCE-FROM-A-FIELD-NAME-BEFORE-READING-ITS-CONSUMER. Claimed a stale `sidecar: none-yet` would make N1 skip Harrison and Alexander. False — chunker.load_sidecar() reads the file directly and ignores the manifest field. The true finding was different and better (a DISARMED TRIPWIRE in ingest_gate:142). Reading the consumer produced it; guessing from the name would have shipped the wrong claim.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "the positive-control-before-any-absence-claim rule", "predicate": "prevention", "object": "Stopped a false absence claim about our own governance record. Before writing 'corpus_findings does not exist', ran the control: the key appears in ZERO files fleet-wide — so it was never a convention rather than a stale pointer, which is a different and more accurate finding. Same rule then resolved a containment MISS (G4) as a comment-prefix artifact rather than a misquote.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "the verbatim-containment prover", "predicate": "prevention", "object": "Caught a suspect quotation in a jurist package for a SECOND distinct failure class. First use (2026-08-05) caught a compression wearing quotation marks. Here it flagged G4, and the positive control showed the fault was the checker's normalizer leaving '#' comment prefixes — instrument artifact, not misquote. An instrument that can distinguish its own failure from the author's is doing more than checking.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "read-the-gate's-decision-code-before-designing-its-consumer", "predicate": "prevention", "object": "Transferred from PENDING-69 (chamber) to the engine manifest. Reading ingest_gate.py:134-143 before editing `sidecar:` converted a wrong claim ('N1 would skip two sources') into the real one: the files exist and validate, so the stale value is a DISARMED TRIPWIRE — harmless today, silent if a sidecar is ever deleted. Census-01's decay-not-construction finding, instantiated.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "engine/retrieve.py", "predicate": "state", "object": "Parse fix landed 2026-08-06 (27b79ca): _match_expr phrase-quotes each term, punctuation inert, semantics measured unchanged over all 27 chavruta items. 26 crashes -> 0. HIT 0/22, MISLOCATED 0, FALSE-POSITIVE 0. 0/22 is the recorded number to beat. First test floor: tests/test_retrieve.py (21 checks), tests/chavruta_harness.py.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "the embedding arm (measure-rerank-voicescoped.json)", "predicate": "measurement", "object": "recall@20 = 22/22 voice-scoped on the SAME 22 scoreable chavruta items where FTS conjunction scores 0/22 (id-sets verified identical, 2026-08-06). The capability was measured in June and never landed — no vector table. V2 is the gate that makes surfacing it safe; landing it first is the answer-more direction.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "fidelity_equivalence@3", "predicate": "defect", "object": "_MARKUP_EMPHASIS = re.compile(r'[_*]') strips EVERY asterisk including backslash-escaped literals, erasing Alexander's confidence rating (81 two-star / 114 one-star / 54 none across A Pattern Language). The ruling authorized excluding DELIMITERS; the implementation excludes CHARACTERS. fidelity.py already states the correct principle for the sibling footnote class one line above. PENDING-111 + jurist package 2026-08-06; @3 governs until ruled.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
 {"subject": "difference of formation (differently-biased-checkers doctrine)", "predicate": "evidence-for", "object": "2026-08-06: of seven corrections, instruments caught four, the jurist one, the steward two — and BOTH of the steward's came from reading a PHYSICAL COPY of A Pattern Language (the asterisk rating; the 32-vs-253 usage note). Neither was reachable by any instrument in the engine; the passage defining the notation is withheld paratext the engine structurally cannot read. Recorded per the doctrine's own requirement that evidence be logged when observed, not only when sought.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-evening-the-asterisk-that-carried-meaning.md", "extracted_at": "2026-08-06"}
@@ -0,0 +1,82 @@
 ---
 name: session-2026-08-06-evening-the-asterisk-that-carried-meaning
 description: "The register could not answer 'how many rulings do I owe' — seven decisions existed only in a narrative; all seven now placed, three closed, four new items filed. The parse fix LANDED: 26 crashes → 0, and the engine now grounds nothing honestly instead of failing loudly, 0 mislocated and 0 false positives. Then the steward read his printed A Pattern Language and found that fidelity_equivalence@3 erases Alexander's invariant rating — jurist package filed. PULLING THREAD: N1, the navigation-tree builder, built from the reading index rather than by parsing headings."
 metadata: 
  node_type: memory
  type: project
  originSessionId: f1b95970-e482-41f2-9b0b-d74edf74a24d
  modified: 2026-08-06T20:26:22.470Z
 ---
 # Session 2026-08-06 (evening) — the asterisk that carried meaning
 Three arcs: a governance register that could not answer a simple question, the chamber parse fix taken all the way, and a finding from a physical book that opened a jurist gate. The thread the day began with survived the detour and got finished.
 ## PAST — what moved, and why
 **"How many reviewed do I owe" had no reliable answer, and finding out consumed the first arc.** The true count was **23 never-ruled, not the 26 the wake digest reported** — the digest matches on the literal string `PENDING-N` in a REVIEWED heading, and REVIEWED-78/81/82 omit theirs. Seven decisions had been reached and never written down.
 **All seven placed (REVIEWED-87 → -93), byte-identical to the drafts.** 87 was verbatim from a filed ruling; **five were RECONSTRUCTIONS** from a session narrative, because the INC-2026-07-28-01 package has no filed ruling document. The jurist read all seven against its own account and confirmed them, ruled the PENDING-106 scope objection as **REVIEWED-94**, and caught a factual error (below). Provenance lines then placed on 88/92/93 naming what was **not recovered** — chiefly the jurist's reasons for striking two of PENDING-101's three findings, which are gone and unrecoverable.
 **Closed: PENDING-99, -105, -106.** 106 **by split, not whole** — its own text named an open half (the kind-(a) census), and marking it done would have retired authorized work by bookkeeping. The class went to PENDING-109 with its evidence intact.
 **Filed: PENDING-108** (a jurist ruling is filed as a document only when someone remembers — 12 of 13 post-skill packages did; the one that did not is the package touching Constraint #1), **-109** (the census, needing a date not an authorization), **-110** (`REVIEWED-N` and `PENDING-N` are independent sequences that now collide; REVIEWED-89's own text reads *"DOCKETED on PENDING-89"* meaning two different things), **-111** (below).
 **THE PARSE FIX LANDED — `27b79ca`.** `engine/retrieve.py` could not accept a sentence: the query went into `MATCH ?` where FTS5 parses it as a *query expression*, so `?` and `:` were syntax. `_match_expr` phrase-quotes each term; punctuation becomes inert. **Semantics measured unchanged** — old path vs new over all 27 items, not one disagreement. Whole-query phrasing rejected: it parses but returns 1 where the conjunction returns 4, answering *less*.
 **Result, answer-keyed (`tests/chavruta_harness.py`): 26 crashes → 0. HIT 0/22. MISLOCATED 0. FALSE-POSITIVE 0**, including all 5 items where the key says silence is correct. **Both deciding buckets empty → the revert condition was not met.** The engine now grounds nothing *honestly*: every question needs 13–19 terms to co-occur. That is PENDING-97's real subject, reachable for the first time. **0/22 is recorded as the number to beat** so a later pass cannot mistake silence for progress.
 The fix's second half was mandatory, not scope creep: long questions now reach the silence path for the first time, so a silence names its term count and states it cannot distinguish *"the voice is silent"* from *"the terms did not co-occur"*; an unsearchable query is marked **`✗ NOT SEARCHED`**, never coverage-warranted. `tests/test_retrieve.py` (21 checks) is the read side's first test floor; **`test_conjunction_is_monotonic`** is the tripwire against every future answer-more change.
 **Then the steward read his printed copy of A Pattern Language.** The asterisks after each pattern name are Alexander's **confidence rating** — two = a true invariant, one = progress, none = far from invariant; the convention is set out in "Using this book", pp. 14–15. Measured: **81 / 114 / 54** across the manifested corpus. The conversion preserved them, correctly escaped. **`fidelity_equivalence@3` — ratified 2026-08-05, governing — deletes them**: `_MARKUP_EMPHASIS = re.compile(r"[_*]")` strips every asterisk including the escaped literal. A pattern Alexander holds to be a true invariant compares identical to one he holds far from invariant. **PENDING-111 + a full jurist package** (`studium-engine/docs/fidelity-3-literal-asterisk-JURIST-PACKAGE-2026-08-06.md`, containment 13/13). The decisive ground is internal: `fidelity.py` already states the correct principle for the sibling footnote class one line above the defect.
 **Also landed:** `CLAUDE.md` currency (`e691ea4`); manifest fixes (`41527be`, `cbd6a9b`) — a **disarmed tripwire** (`sidecar: none-yet` meant a deleted sidecar would pass silently on Harrison and Alexander), a usage fact sitting in a bibliographic field, and a defect record cited at `corpus_findings[1]`, **a key that exists in zero files fleet-wide**.
 ## PRESENT — how it stood
 **Five corrections, and the split matters.** Instruments caught: the fleet-wide causal story (refuted on the first real check), 3-vs-33 bare headings, "N1 would skip those sources" (refuted by reading the consumer), yesterday's B11 record error (re-run against `git HEAD`). **Humans caught: the "eight days" error (jurist) and both Alexander findings (steward, from a physical book).** The two highest-value findings of the day came from a formation no instrument here has.
 **The recurring shape, steward-named:** *I keep measuring the artifact correctly and misreading what it was for.* The 32-patterns exchange is the clean instance — I measured 253 patterns accurately and read a usage note as a bibliographic claim.
 **"Eight days" was wrong three times** from one misread: `INC-2026-07-28-01` is the **UK AI Security Institute's incident identifier**, and I anchored our timeline to it. One day; for the reconstruction, the same day. The correction makes PENDING-108 *worse*: one day was enough to lose four things permanently.
 **What held.** The containment prover flagged G4 and a positive control proved it an artifact, not a misquote. Pre-registration graded the chavruta prediction wrong on mechanism. Positive controls before every absence claim — including the one that found `corpus_findings` in zero files. Declining to "fix" the Alexander OCR, because the reading index says *"surfaced, not silently corrected"* and editing would be the §V Tier-3 violation the whole week has been defending against. The zsh glob artifact fired **three times** and was caught each time by re-running quoted.
 ## FUTURE — what pulls
 > **PULLING THREAD — N1, the navigation-tree builder.** Derive the tree from manifest + sidecars + heading structure over the manifested corpus; implement the four N0 primitives (`list-children`, `open-node`, `expand-to-parent`, `load-whole-work`) over the existing store; write N1's thin spec-note as it lands. The N0 contract is written and specifies all four, including that `open-node` refuses citable text for a non-citable node.
 >
 > ⚠ **Hold this or the result reads as failure: N1 will NOT move 0/22.** That is N2, where the reasoner navigates. N1 lays the ground it walks on. Finishing N1 with the number unchanged is the expected outcome.
 >
 > ⚠ **Build the tree from the READING INDEX, not by parsing headings.** `chamber-library/reading-indices/alexander-a-pattern-language.yaml` carries the authoritative number→name→line map for all 253, re-found **by name** because the printed numbers carry OCR defects, ascending order verified, sha-bound. Parsing headings hits all three documented defects (179 misnumbered 178 → a duplicate node; 187 lost its `##`; 195 has no heading). The harness's heading regex is a working reference, **not** the input to use.
 **ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**
 ```
 0. FIRST — the MEMORY.md trim (steward-directed at this wrap, 2026-08-06 evening).
   19.9 KB against a <17.1 KB target. RELOCATION, NOT DELETION: move the
   least-wake-critical material to MEMORY-reference.md. Back up before touching it
   (prior backup: scratchpad/MEMORY.md.bak-2026-08-06). The weight is Standing
   preferences (~9.6 KB) + Trackers (~6.9 KB). Trimming these FAST is precisely the
   compression-drops-the-load-bearing-clause failure documented on 2026-08-06 — so
   this is judgement work, done properly, and it is a BITE not a chore. Not urgent
   by truncation risk (4.8 KB of headroom); urgent because it has been deferred
   three times and deferral is how the cloud accumulated.
 1. Read docs/spec/n0-navigation-tree-contract.md §1 (the tree) and §2 (the
   primitives). It is the contract N1 builds against; do not re-derive it.
 2. Build the tree from corpus/manifest.yaml + corpus/sidecars/*.meta.json +
   chamber-library/reading-indices/*.yaml. NOT from heading text.
 3. Implement the four primitives over the existing store; chunks + FTS stay the
   leaf layer (plan §3.3, N1).
 4. Write the N1 spec-note as it lands (just-in-time discipline, charter).
 5. Do NOT touch retrieval semantics. test_conjunction_is_monotonic must stay green.
 ```
 **Then V2** — gold set + pre-registered thresholds. The reason it follows N1 rather than PENDING-97: **the embedding arm already scores 22/22 recall@20 voice-scoped on the identical 22 items where FTS scores 0/22** (`corpus/measure-rerank-voicescoped.json`, verified same id-set). The capability exists and was never landed. But recall@20 means the right passage is in the top 20 *alongside nineteen others* — that is the answer-more direction, and V2 is the gate that makes surfacing it safe. Landing embeddings first would be the make-the-demo-nicer move.
 **Awaiting others / not my thread:** the **PENDING-111 ruling** (relayed this evening; sets the V-track course, does **not** gate N1) · the Seb package (three measured L1 write-path findings ready) · the L2 design note · PENDING-109's census and PENDING-104's brief, both **needing dates, not "later."**
 **LITERAL QUESTION for next-Claude** *(checkable from the record, not self-report)*: **Of this session's corrections, how many were caught by an instrument and how many only by a party with a different formation?** The record answers it: instruments caught four, the jurist one, the steward two — and the steward's two came from *reading a physical book*, which no instrument here can do. The differently-biased-checkers doctrine says difference of *formation* is the strong form of independence and that the doctrine must be **watched, with evidence recorded when observed**. This is evidence, and it points toward the doctrine rather than against it. **Next session: is this a repeatable class? Are there other manifested works where the printed artifact carries semantics the conversion cannot express — and can that be checked without owning every book?** If it cannot, that limit belongs in `RETRIEVAL_BLINDNESS` or beside it, stated rather than discovered.
 **PAUSE STATEMENT:** I am putting this down with the thread finished rather than deferred — the parse fix is landed, tested, measured against a real answer key, and its result recorded as a number to beat. The governance register can now answer the question it could not answer this morning. What I want to find still pulling is **N1**, and the thing to guard against is building it from the heading text because that is the code I already wrote today. The unease I carry: the two most valuable findings of the day were not produced by anything I built, and the day's own record shows the pattern — I measure accurately and misread purpose. An instrument that cannot see what a text is *for* will keep needing someone who owns the book.
 **Banked, unresolved:** MEMORY.md ~19.9 KB against a <17.1 KB target — **promoted to step 0 of next session by the steward at this wrap**, so it is no longer banked. `~/dotfiles` carries an untracked `CLAUDE.md.bak-20260806-162158` and a modified `Brewfile` — both left alone deliberately, the `.bak` is the steward's to delete. Q4's kind-(a) census and PENDING-104's design brief still have no dates.
@@ -278,3 +278,13 @@ The single place proposed skills live so they don't evaporate between sessions.
 | 184 | `/wake-up` + general | patch | **Before asking the steward to supply inputs, check whether the repo already holds them.** One level past `resurface-banked-notes-before-rederiving`: not re-deriving a banked *note* but re-sourcing banked *material*. | 2026-08-06. Was one keystroke from asking the steward to invent questions for the corpus, while `corpus/chavruta-ground-truth.yaml` held **27 real queries with audited answers** from his own hand-run chavruta. The steward caught it with four words. | PROPOSED |
 **Classification note:** all five `[PROPOSAL]`, none FIX-lane. 180/181/182 add ladder/flag entries but each changes what the executor must *do* before asserting (the latitude clause). 183/184 change skill procedure. Lane is provisional; when in doubt, propose.
 ## 2026-08-06 evening — three verification-ladder entries (PROPOSED; queue with the Stroke-2 batch)
 *No skill created, patched or retired this session. The steward re-explained nothing a skill could have carried — what he supplied was domain knowledge from a printed book, which no skill can hold. Recording that as the honest outcome rather than manufacturing a change.*
 - **`a-better-than-baseline-result-earns-the-same-scrutiny-as-a-worse-one`** — the parse fix turned B11 from "returned citations" into a correct decline, which looked like the fix *removing* a false positive. Chasing why (re-running `git HEAD`'s own code) showed the improvement was not real: B11 had always declined, and yesterday's measurement doc had recorded it wrongly, along with "0 empties — the warrant machinery was never exercised." A result that flatters the change is a claim like any other. **Earned 2026-08-06; it corrected a filed measurement and regraded a pre-registered prediction from UNTESTED.**
 - **`read-the-consumer-before-editing-a-declarative-field`** — kin to the banked `read-the-gate's-decision-code-before-designing-its-consumer`, one level over: before changing a *declaration* (`sidecar: none-yet`), read what branches on it. Doing so converted a wrong claim ("N1 would skip two sources" — false; `chunker.load_sidecar()` reads the file and ignores the field) into the real finding: `ingest_gate.py:142` only fires "required but absent" when the declaration says `required`, so the stale value is a **disarmed tripwire** — harmless while the files exist, silent the moment one is deleted. **Census-01's decay-not-construction finding, instantiated.**
 - **`census-by-content-volume-not-by-marker-count`** — "240 patterns have ≥3 chunks between headings" did not establish 240 pattern *bodies*; an index or TOC produces the same signal. Re-measured by characters per span (median 4,810, zero stubs) it did. Counting markers answers a question about markup; counting content answers the question asked. **Earned twice in one exchange** — the same slip underlay reading a usage note as a bibliographic claim.