docs(memory): redirect the next wake to a research session, not the chamber thread

Steward instruction at wrap: the next session is a short research session on a very recent incident touching this work; everything else defers to the following morning. Without this the wake reads 'pulling thread: ask the corpus real questions' and opens the wrong work. Also records the two things bearing on doing it well: the May-2026 cutoff against an August-2026 'recent' incident (search, don't recall, mark sourced vs inferred), and a caution against pre-fitting the incident to a thread we already like — the failure this whole session was a study in. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AB3Kryoy6b1pm2Nz1DYdLh
2026-08-05 22:08:35 +02:00
parent 8b72b149f9
commit ef8cb04340
2 changed files with 14 additions and 0 deletions
@@ -67,6 +67,8 @@ permalink: claude-memory/memory
 - [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 SESSION IS A SHORT RESEARCH SESSION, not the chamber thread.** Steward instruction 2026-08-05 evening: opens on a **very recent incident touching this work**, which the steward names on arrival. All chamber/engine work below — the retrieval measurement, the 5 skill-harvest proposals, REVIEWED-87's placement — is **deferred to the following morning**. ⚠ Cutoff is May 2026, today is August 2026: **search, don't recall**, and mark sourced vs inferred.
 - [Session 2026-08-05 — the quoted tier accepts three of seventeen](session-2026-08-05-the-quoted-tier-accepts-three-of-seventeen.md) — **The engine's quoted tier measured against real human citation for the first time: 3/17 accepted, and the largest single cause is a FULL STOP, not markup** (+5 vs +3). `verify_quote`'s first production call — it located the known mislocation unprompted (`found-elsewhere: 1181`). **Four of my claims died today**: the markup framing; a census flag I raised→withdrew→had to UN-withdraw (the withdrawal *inferred a breakdown from a total*); a forward-window locator that reported a spurious uniform offset **twice** (Δ−30, Δ−25 — truth is Δ−1); and Q1's rationale, overturned by the jurist. **`fidelity_equivalence@3` RATIFIED + BUILT** (REVIEWED-87 drafted, **not yet placed**) — pre-registered 3/17→6/17, then measured exactly that; suites 22/22 · 43/43 · 24/24. **The conversion runbook has NEVER parsed** (8/8 commits; fixed `4f8ad64`). **PENDING-86 (a)+(d) built** — jurist given `chamber-spec` + `governance_search`; **the ruling changed materially the moment it could read primary text**, and its structural pass found REVIEWED-11/-12/-74 hidden from `item_spans` by indentation (steward unindented; 78→81 items). **The finding that cuts inward: the decisive §II.3 sentence was in my own read output and I did not surface it** — containment verifies that what you quoted is ACCURATE, never that you quoted what MATTERS; limit now written on the instrument. P5 executed (Δ−1 uniform, sha-bound, composite split applied); PENDING-99/100 filed. ⚠ Said *'Symmetria active'* at wake and never invoked it — decorative line, no ledger today. **PULLING THREAD unchanged and one day older: ask the corpus real questions.** Second consecutive day on scaffolding — every step steward-directed, so not drift as a choice, but drift as a result.
 ## Historical reference → MEMORY-reference.md
@@ -46,6 +46,18 @@ I was an hour from filing "markup breaks the gold." **The largest single cause i
 ## FUTURE — what pulls
 > ### ⛔ READ THIS FIRST — the next session is NOT this thread
 >
 > **Steward instruction at wrap, 2026-08-05 evening:** the next session opens as a **short research session on a very recent incident that touches this work**. The steward will name it on arrival. **Everything below — the chamber thread, the resumption point, the open proposals — is explicitly deferred to the following morning.** Do not open the chamber work, do not start the retrieval measurement, do not act on the skill-harvest proposals or place REVIEWED-87. Wake, acknowledge, take the research request.
 >
 > **Two things that bear on doing it well:**
 > 1. **The assistant knowledge cutoff is May 2026 and today is August 2026.** An incident described as *"very recent"* is almost certainly **outside training**. Do not answer from memory — that is the exact shape of confabulating the rare specific. **Search the web**, and say plainly what is sourced versus what is inference.
 > 2. **"Touches upon our work"** most plausibly means one of: AI governance / oversight failure · memory or context substrate failure · verification, provenance or citation integrity · the contamination problem (models optimising for the interlocutor) · AI-assisted authorship and attribution. Let the steward's framing lead; do not pre-fit the incident to a thread we already like — that is the failure this whole session was a study in.
 >
 > *(This block was written at wrap, before the steward named the incident. If it is named in `MEMORY.md`'s Active Session line, that is the more specific record — prefer it.)*
 **PULLING THREAD (inherited, unchanged, one day older): ask the corpus real questions and let that settle Chamber V1's voice-set.** The instruments are now materially better — the quoted tier accepts 6/17 instead of 3/17, `verify_quote` has a production caller, the jurist can read primary substrate, P5's anchors are content-verified. None of that is the point. The point is the thirteen and what V1 is *for*.
 **ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**