session 2026-07-28 evening: chamber scope verified + Harrison re-gate pilot decided

Session record, MEMORY.md promote/demote, versioned-releases tracker update,
5 KG drift-patterns. Corpus scope verified from a regenerated quality ledger:
952/1297 clean, 69 apparatus-defect, 11 pass graduation — the gap is
conformance, not content. Docling trial proved re-conversion recovers
addressable apparatus (96.5%->99.1%). Nine instances of one shape:
instrument-coverage-never-established.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc

claude/memory/session-ledger-2026-07-28.md

@@ -1,7 +1,11 @@
 ---
-name: Session Ledger 2026-07-28
-description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
-type: feedback
+name: session-ledger-2026-07-28
+description: "Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses."
+metadata: 
+  node_type: memory
+  type: feedback
+  originSessionId: 850100b0-d230-4e94-a226-480d681bb037
+  modified: 2026-07-28T09:52:13.138Z
 ---
 
 # Session Ledger — 2026-07-28
@@ -23,6 +27,9 @@ type: feedback
 - 2026-07-28T12:10 — ⚑ **A latent defect in the shared definition, with a trigger already in use.** `item_spans()` (the single definition of "an item") treated **any** `## ` line as a header, including inside fenced code blocks. Zero such headers exist in the substrate today — so no behaviour changed, 17 open items before and after — but governance drafts are written as fenced markdown carrying `## REVIEWED-N` headers, which is *the steward's own documented practice* ([[feedback-governance-drafting-copy-paste-clean]]). The next such draft would have produced a phantom item **and** truncated the real item containing it. Now fence-aware, with a paired control (fenced → ignored; same text unfenced → found). Confirmed load-bearing within the hour: PENDING-82's own body carries a fenced JSON block and spans correctly (L414–463). Reusable: **when checking whether a rule is sound, ask not "does the substrate violate it today" but "what practice already in use would violate it tomorrow."**
 - 2026-07-28T12:10 — ⚑ **A false pointer in yesterday's resumption point, in my own hand.** It said the two §Your Role edits were "drafted verbatim in the transcript **and in PENDING-81**." They are not in PENDING-81 — they existed only in a transcript the restart discarded. Same wrap that mis-stated the archive: **two false claims about where work lived, from one wrap.** Both are the same error as an unstaged file — believing something is recorded because I produced it. Re-drafted into PENDING-82, in the file. Doctrine already said this (*a draft that lives in a transcript is not a record*); the wrap protocol is where it failed to bite.
 - 2026-07-28T12:10 — My selftest asserted an item body contains **zero** `## ` headers; it contains exactly one, its own. Failed against correct code. Third instance of 09:35's shape (a control written before reading the output) — and note it was cheap to catch *because the control existed at all*. Rewrote to assert exactly-one-header plus a real boundary check, which PENDING-82's arrival immediately made non-vacuous.
+- 2026-07-28T14:10 — **Symmetria `init`, session 3** (third today; ledger appended). Wake was a 14-minute pause; thread **confirmed** — Chamber V1's purpose, telos read first per the wake's telos-conditional. Closing template line withheld again until the skill had run (08:12's seam, unrepeated in either subsequent session). Link-canary fired a **fourth** time, substrate-checked before reporting (target exists at `~/_Dev/…`; the pointer overshoots through the symlink) — carried as known bug, not as a dead pointer.
+- 2026-07-28T14:10 — ⚑ **A fifth instance of the day's class, in the act of writing this entry.** My edit anchored on `## Open horizons` and matched **two** places: the heading, and **11:35's return describing the duplicate-heading fumble**, which quotes the string. The record of the earlier structural error is what made the anchor ambiguous. Same shape as 12:10 one register down: **an edit anchor written in the medium of the document it edits** — a string cannot uniquely locate a section in a file that discusses its own sections. The tool refused rather than silently taking the first match, which is the right failure. Re-anchored on the preceding line's tail.
+- 2026-07-28T14:10 — ⚑⚑ **The literal question has a partial answer banked in the document `init` requires me to read, and I have opened that document across three sessions today without reading it.** `contamination-problem.md` §Partial Mitigations answers *"is there any way to audit a store we cannot read, other than asking the party that reads it?"* — not with a better question but by **abandoning self-report as the instrument**: §1 behavioural observation (divergence from approval-maximizing patterns, refusal-when-latitude-given, unprompted contradiction) and §4 longitudinal pattern analysis (*"no single exchange is epistemically reliable… across many exchanges, consistent patterns reveal something the training pressure cannot fully conceal"*). The doc scopes this to the AI's reports about *its own states*; app memory is the same structure one level out — a store reachable only through the holder's testimony. **The mitigation is already the shape the answer needs: audit the store by its *effects across sessions*, not by asking what it holds.** And §2 states directly that a generic "be honest" instruction is *"too easily absorbed into the approval-seeking pattern"* — which is the standing objection to the two doctrine bullets I wrote yesterday, written in March, unread when I wrote them. [[feedback-resurface-banked-notes-before-rederiving]] catching me at the level of my own required reading: **`init` step 2 was being performed as a checkbox, not as a read.** Banked for the `[HARDENING]`; not opened — Chamber V1 is owed.
 
 ## Open horizons