session 2026-09-09: REVIEWED-136 + AMD 1, the Tarbuckle fortnight read, PENDING-180, and the session record

The lapsed 2026-09-08 obligation, closed. Session memory, ledger, KG (7 lines),
skill-harvest proposals A and B, and the demote-on-promote of the 09-06 Active
Session block into MEMORY-reference.md.

Pulling thread: an unruled record is read as ruled — which is not a replacement
for the floor but what the floor cannot measure.

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

claude/memory/session-ledger-2026-09-09.md

@@ -0,0 +1,55 @@
+---
+name: Session Ledger 2026-09-09
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-09-09
+
+## Returns
+
+- **2026-09-09T~13:00 — the wrap's own first move was stale.** The inherited resumption point said
+  PENDING-139's re-measurement *"lives only in a commit message."* Substrate-checked before acting:
+  commit `58b7409` (2026-09-06) filed it into the item as an additive note; leg (A) reads REPAIRED,
+  leg (B) confirmed live at `governance-drift-check.py:774`. Would have asked the steward for an act
+  already taken. ⚠ **Not** an instance of the inherited question — the note is my own hand, i.e.
+  failure condition (ii), the proofreading habit.
+
+## What held
+
+- N-now re-measured rather than relayed, by the trial's own method plus the ground-truth mumble
+  signature: **62 = 38 real + 24 mumble (38.7%)**, down from 65 on 09-03. The mumble term is
+  unchanged at 24; the whole fall is real sessions leaving the 30-day window.
+- The digest's "unattended session" flag was opened rather than reported: `e9e5ce1d` is a 19 KB
+  local-command artifact written at the same minute as the 09-06 wrap, not an executor run.
+- `thread-query` returned nothing bearing on the thread. Recorded as a null result, not padded.
+
+## Open horizons
+
+1. **PENDING-162 came due 2026-09-08 and passed unobserved.** No ruling in the register; the
+   8 September read did not run. The date-triggered obligation is now one day stale — the exact
+   class banked as [[feedback-a-dated-measurement-is-not-a-status]].
+2. **The floor** — the pulling thread, untouched. No rule set; 54 is still maintained by nothing.
+3. Joint PENDING-178/-179 ruling, before 2026-09-16.
+4. The 8 RECORD-AND-CLOSE items, executor-able on a word.
+5. Digest: one STOPPED worker still ARMED with `--reply-on-resume` (`acaabadf`). Whether the daemon
+   respawns a *stopped* job is unestablished.
+
+## Confidence to recalibrate
+
+- **Verified against substrate this wake:** PENDING-139 legs (A) and (B) by reading the code and the
+  item body; N-now and its composition by enumeration over all 62 transcripts; the absence of any
+  REVIEWED entry after 135/AMD-1; repo HEADs; dotfiles log since 09-06.
+- **Inherited, not re-verified:** the 54-item queue figure; the 43-vs-20 weighing of the two floor
+  rules; the digest's parked-worker reading.
+- ⚠ **Post-pause:** three days of context loss. Everything above the "verified" line came from files
+  read this session, not from recall.
+
+## Authorization moves
+
+- None yet. PENDING-162's lapse is a steward-and-jurist matter; the executor surfaces it and does not
+  run the compromised read on its own motion.
+
+## Sub-agent dialogues
+
+## Bypasses