[FIX] Resolve the STATE-CLAIM; [HARDENING] file PENDING-163; add the preservation instrument

STATE-CLAIM: memory-index-claims-reviewed-127-unplaced -> resolved, pointing at
7a92460. Verified end to end by re-running governance-drift-check.py rather than
trusting the write: "1 of 3 open are NOW FALSE" -> "2 tracked, none falsified /
plus 1 RESOLVED", no dangling-pointer defect, so the resolution parses AND its
pointer resolves. The `resolved:` form was derived from the parser, not from
memory of the schema, which is also why the correction commit had to come first.

What that discharge is evidence for is written into the item so it cannot be
quoted as more: one marked claim, marked by its own author, corrected in the
immediately following session. Expressibility, not adoption. The 57 unmarked
claims are untouched.

PENDING-163 [HARDENING]: the global pre-commit hook refuses files over 5MB and
prints "Consider using Git LFS", but measures `wc -c < "$file"` — working-tree
size — so an LFS-tracked file stages as a ~130-byte pointer and is still refused.
Tried it; same refusal, same file. The hook is NOT modified: it is global and
governed by REVIEWED-100/105.

preserve-transcripts.py: PENDING-147 option (i). The archive itself is NOT in this
repo — 115MB of transcripts is not dotfiles material, which is what the hook was
right about even though its reasoning measures the wrong thing. It lives at
~/_Dev/claude-transcript-archive, outside the harness's pruned path, which is what
actually stops the clock. 43 transcripts, read-back PASS.

No guard was bypassed: no --no-verify, no per-repo core.hooksPath override, and no
empty .git left behind that would make the archive look tracked when it is not.

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

claude/memory/MEMORY.md

@@ -79,7 +79,7 @@ permalink: claude-memory/memory
 > ⚠ **THE WRAP SEAM FAILED, WAS DIAGNOSED, FIXED, FIRED, AND WAS THEN REJECTED — all after the wrap.** The heartbeat proved the `Stop` hook was firing all along, so the silent-net prediction was **right that it would fail and wrong about why**. The detector sought the steward *typing* `/wrap-up`; the wrap arrived as prose + a Skill call. ⚠ **The earlier, correct fix is what blinded it.** PENDING-160's sixth and sharpest instance.
 > ⚠ **PENDING-162 `[ESCALATE]` — the executor breached REVIEWED-128 condition 3** within seven hours, reading the rejection log for content while diagnosing. **Conditions 1 and 2 were made structural; only 3 was left to care.** ⚠ It surfaced the clustering signal (2 seam rejections, 10 and 11 words vs a cap of 9) that the fortnight was meant to arbitrate — **not acted on, and must not be.**
 > 📌 **STEWARD OWES:** place the REVIEWED-129 amendment · rule PENDING-160 · **restart Claude Desktop** or `governance_pair` is absent · the §5 regrade ruling.
-> ⚠ **DELIBERATELY NOT FIXED:** the `STEWARD OWES: place REVIEWED-127` line now sits in `MEMORY-reference.md` with this block's predecessor. It is **false**, it is **marked** by `STATE-CLAIM: memory-index-claims-reviewed-127-unplaced`, and correcting it is **next session's agreed first act** — carried forward rather than discharged as a side effect of this rotation.
+> ✅ **DISCHARGED 2026-08-26 — the agreed first act, done.** The false `STEWARD OWES: place REVIEWED-127` line in `MEMORY-reference.md` is corrected (`7a92460`), **struck rather than deleted** so instance six keeps its evidence, and the `STATE-CLAIM` block carries `resolved:` with that pointer. ⚠ **This is one marked claim corrected in the very next session — evidence for expressibility, NOT for adoption**, which is the open question (REVIEWED-127 C2). The 57 unmarked claims are untouched.
 
 - [Session 2026-08-25 evening — Tarbuckle wired, and the gap controls cannot see](session-2026-08-25-tarbuckle-wired-and-the-contact-gap.md) — five surfaces built and every one failed on first real use; PENDING-151 step 1 + step 2 both run. **NEXT: the §5 regrade gate — the control is already degraded and decays with every exposure.**
 

claude/memory/session-ledger-2026-08-26.md

@@ -0,0 +1,90 @@
+---
+name: Session Ledger 2026-08-26
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-08-26
+
+## Returns
+
+- 2026-08-26T~wake — `/wake-up` ran; Symmetria `init` at its close (the clasp's lineage hand).
+  N-now **re-measured, not relayed**: **43**, down from 51 on 08-25. The obligation found it,
+  not the vigilance — same shape as PENDING-147's own disclosure.
+
+- 2026-08-26T~afternoon — **Chose the wrong container and the guard caught it.** Put the
+  archive in `~/dotfiles` by habit, because the governance record lives there, without asking
+  whether 115 MB of raw transcripts is dotfiles material. The pre-commit hook refused it. The
+  return was reading the refusal as a **fit signal** rather than an obstacle — τὸ πρόσφορον —
+  and moving the archive rather than moving the guard.
+- 2026-08-26T~afternoon — **Three chances to bypass a guard, none taken:** `--no-verify`, a
+  per-repo `core.hooksPath` override, and leaving a `.git` with no commits behind (which would
+  have made the archive *look* tracked). ⚠ The third is the one I nearly did by inertia; it is
+  the same shape as the hook's own doctrine that *a disarmed hook must not look like an armed one*.
+
+## What held
+
+- Ran `thread-query.py` on the actual thread and reported the **null honestly** (689 candidates,
+  nothing on-thread). A step that can only conclude "keep it" is not a trial.
+- Did **not** run the literal question's grep at wake. The question is held open, per the wake's
+  own constraint; and `tarbuckle-rejects.jsonl` was not opened — REVIEWED-128 condition 3.
+- Substrate-checked before calling anything outstanding: PENDING-147 (i) verified **unbuilt**
+  (no `claude/governance/transcripts*`, no git-tracked copy, no REVIEWED entry) rather than
+  read off its own recommendation line.
+
+- Verified the STATE-CLAIM resolution **end-to-end by re-running the instrument**, not by
+  trusting the write: `1 of 3 open are NOW FALSE` → `2 tracked, none falsified / plus 1 RESOLVED`,
+  with no dangling-pointer defect, so both the `resolved:` parse and its pointer were proved.
+- Derived the `resolved:` form **from the parser** (`governance-drift-check.py:299,486,498`),
+  not from memory of the schema — and therefore made the correction commit FIRST, because
+  `pointer_resolves()` requires a commit that already exists. The say–do seam, avoided by ordering.
+- Applied the *filed-a-non-defect-as-a-defect* flag **before** filing PENDING-163: stated the
+  working-as-intended reading first, then the argument against it, and kept the claim narrow
+  (the check and its printed advice disagree) rather than "the hook is broken".
+- Preserved **all 43** transcripts rather than the 23 the item scoped, because the files expiring
+  soonest are the ones outside its scope — and said so in the README rather than letting the
+  wider action pass unremarked.
+
+## Open horizons
+
+1. **Agreed first act:** correct the false `STEWARD OWES: place REVIEWED-127` line now in
+   `MEMORY-reference.md`; set `resolved:` on the `STATE-CLAIM` block in `PENDING.md` with a
+   commit pointer. Carried deliberately across the rotation rather than discharged by side effect.
+2. **PENDING-147 (i) — preserve the post-2026-08-07 transcripts.** Needs no ruling by its own
+   text. Earliest cohort deletes **2026-09-06**. ⚠ The only open item whose cost rises daily,
+   and N-now falling 51→43 in one day is that deletion happening in view.
+2b. ⚠ **The archive has NO BACKUP.** Preserved from pruning; lost to a disk failure. The
+   steward's call: leave it, add a remote (a disclosure question — raw transcripts are more
+   verbose than the session memories that already reach `git.skemantix.com`), or Time Machine
+   it. **Cheapest fix for the actual gap is not git.**
+2c. **PENDING-163** filed — the pre-commit hook's 5 MB check reads working-tree size, so the
+   Git LFS remedy it prints cannot satisfy it. Not urgent; nothing is blocked.
+3. **The §5 regrade gate** — steward's and judge's to settle, not the executor's. The honest
+   outcome may be to record the control as degraded rather than run it and call it a control.
+4. Steward-owed: place the REVIEWED-129 amendment · rule PENDING-160 · restart Claude Desktop.
+5. Dated, 2026-09-08: two obligations in one sitting — mumble rate report + rejection log deletion.
+
+## Confidence to recalibrate
+
+- ⚠ Yesterday's finding is still the governing caution: **controls verify the code, not the
+  contact.** Anything built today is untested at the seam with a model, a shell, or a corpus
+  containing its own reader — and no control written today will see that either.
+- ⚠ **Care failed inside a day** on REVIEWED-128 condition 3 (PENDING-162). Conditions made
+  structural held; the one left to care did not. Prefer a mechanism over a resolution today.
+- ⚠ Bias observed twice on 08-25: **filing a non-defect as a defect.** Before calling something
+  broken, ask whether it is the rule working.
+
+## Authorization moves
+
+- **PENDING-147 option (i) executed WITHOUT a ruling**, on the item's own text — *"copying files
+  preserves evidence and changes no instrument, no doctrine and no ladder."* ⚠ **The option
+  bundles a second act the same sentence does not license:** *"re-express the trigger over the
+  preserved set"* changes `governance-drift-check.py`, which REVIEWED-95's falsifier leans on,
+  inside a trial under the REVIEWED-123 freeze. **Split; only the copy was done.** The archive is
+  currently inert with respect to every governance gate, and its README says so on its face.
+- **PENDING-163 filed `[HARDENING]`, hook NOT modified.** It is global to every repo and governed
+  by REVIEWED-100 / REVIEWED-105; changing what it measures changes what it permits everywhere.
+
+## Sub-agent dialogues
+
+## Bypasses