session 2026-08-13: REVIEWED-119/120 placed; MCP key descriptions refreshed

⚠ THIS COMMIT'S CONTENTS ARE MIXED, BY EXECUTOR ERROR, AND THE MESSAGE NOW SAYS
SO RATHER THAN DESCRIBING ONLY ONE PART. The original message named only the
governance-mcp.py change; `git add -A` had swept four other files. Amended before
push, so no shared history is rewritten.

What is actually here:

1. REVIEWED-119 and REVIEWED-120 (REVIEWED.md, +38) — STEWARD acts, placed during
   this session. 119 authorizes PENDING-135 option (c), instance 8 reclassified as
   a negative-candidate with the sub-type name held open, and corrects the item's
   own claim that option (d) was blocked cross-repo (the constraint is
   studium/v2-gold@1 §14.2, engine-side and D-1, not the chamber-locked
   studium/meta@1). 120 authorizes PENDING-136 option (c), retiring bare
   `distinct_spans`.

2. PENDING-135, PENDING-136 and the PENDING-131 Addendum 4 defect-count fix
   (PENDING.md, +212) — executor filings, and the ones that legitimately belong to
   a session wrap.

3. The session ledger (claude/memory/session-ledger-2026-08-13.md) — likewise.

4. governance-mcp.py (+24) — the [FIX] the original message described: two V0-lane
   key descriptions had gone stale the same day the dispositions landed.
   PENDING-134's H1 holds the doctrine ruling until those keys are actually SERVED
   (the running client keeps the old eight-key map until restart, which is steward
   action and still pending). The descriptions are what the jurist reads to decide
   which key to OPEN, so a stale index served at first contact would mislead on
   first contact — the class this whole arc is about. Selftest 54 checks, 0 failures.

5. Brewfile (+1, `mas "NordVPN"`) — NOT this session's work. It belongs to
   sysupdate's sweep and was swept in by the same error. Left in place rather than
   surgically removed: extracting it would rewrite more than it repairs, and the
   line is already accurate. Recorded so the next reader is not misled about which
   process authored it.

The wrap protocol's §6.5 requires a scoped add for exactly this reason — the
steward's in-progress changes belong to the steward's sweep, and a governance
act placed by the steward must not be recorded under an executor's message.

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

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

@@ -0,0 +1,136 @@
+---
+name: session-ledger-2026-08-13
+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: 1524bae7-44b3-4ba9-8c36-24f53bc8acae
+  modified: 2026-08-13T17:42:52.803Z
+---
+
+# Session Ledger — 2026-08-13
+
+## Returns
+
+- **Wake — substrate-checked a disposition clause instead of reporting it.** REVIEWED-118's
+  `**If AUTHORIZED:**` line reads as a completed act ("Retract instances 6, 12 and 16 …").
+  Checked: `REVIEWED-118` appears nowhere in `corpus/` or `docs/`, and L926's instances still
+  stand in `corpus/mauss-phase2-spans.yaml`. **Authorized, not executed.** Reported as the
+  unblocked next act rather than as done — the wake-step's own discipline (*a disposition clause
+  is not a status*), which exists because the wake is the highest-leverage place a false claim
+  can land.
+
+- **Read the MARKED key's verdict field, not the word count.** First tally counted every
+  occurrence of the three verdict words and returned 38/33/6 — inflated by the legend table that
+  defines the vocabulary. Grepping the actual `**VERDICT:**` field gives **32 `does-not-ground`,
+  4 `grounds`, 0 `cannot-judge`** over 36. Same shape as 2026-08-09's neutrality check matching
+  its own legend: a measurement counting its own documentation.
+
+## What held
+
+- The link-resolution canary ran **as a script at SessionStart** for the first time (dotfiles
+  `32b0c9d`, built 08-10 against the 08-09 steward to-do). 378 pointers + 31 wikilinks, 0 dead.
+  The described-not-invoked gap is closed; it was not retyped this wake.
+
+## Open horizons
+
+- **No wrap record for 2026-08-10.** A large day — the Alexander eight, the gold-intersection
+  reporter, the jurist package, the MARKED answer key, four rulings placed (115–118) — survives
+  only as a mid-day ledger written at 14:10, before any of the afternoon's commits. The 08-09
+  session's PAUSE STATEMENT is therefore the newest wrap, and it is four days stale.
+- **`wrap_inside` detector, second consecutive firing.** Named on 08-10 as a two-valued detector
+  over three cases (wrapped · wrapped-then-continued · never-wrapped). On 08-10 it was a false
+  alarm. Today it appears **true** — at least one session did not wrap. A detector that cried
+  wolf once and is right the next time is the worst position for it to be in. Still unfixed.
+- ~~studium-engine ahead 8, unpushed since 08-10 18:11.~~ **CLOSED** — pushed 2026-08-13
+  (`92a97d0..e51e30d`, 9 commits). The 08-10 arc left the single local copy: the Alexander eight,
+  the gold-intersection reporter, the jurist package, the MARKED answer key, and today's
+  retraction. `main...origin/main`, in sync.
+- REVIEWED-118's retraction window is stated as time-limited by its own ground: the fixture is
+  quiescent *now*, and "that window closes as soon as anything starts measuring again."
+
+- **Caught mid-execution: the spans file is GENERATED.** `scripts/bind_mauss_spans.py` writes
+  `corpus/mauss-phase2-spans.yaml` whole (hardcoded header + `yaml.safe_dump`). A retraction
+  recorded only in the emitted YAML would be erased by the next regeneration, silently, with no
+  diff to read — the disarmed-tripwire class. Found by grepping consumers before writing, not
+  after. The block went into the generator as well.
+
+- **Caught before writing: the two files hold different claims.** REVIEWED-118 says "retract …
+  from the grounded set in [spans file] and [tags file]", but the spans file's own header says in
+  capitals *"WHAT THIS FILE DOES NOT ESTABLISH: that any span ENTAILS the claim."* It measures
+  BINDING, and instances 6/12/16 genuinely do locate to L926 — that stays true after the
+  retraction. Deleting a true measurement to express a judgment about a different property would
+  have made the file stop meaning what its header says. Recorded there, retracted in the tags file.
+
+- **The YAML parse check caught my own hand-edit.** An unquoted colon inside a plain scalar
+  (`"recorded below: these three instances"`) broke the file. `yaml.safe_dump` would have quoted
+  it; the hand-edit did not. Exactly the drift the generator note above is about, arriving
+  immediately as a live instance rather than an abstraction.
+
+- **Steward-caught, twice, on the same instrument — and both times the challenge was to an ASIDE,
+  not to a number.** (1) "fiction can be very valuable too", against my parenthesis *"musil (0,
+  longest span 104 chars, and fiction)"*. Checking it found the census's **fourth** defect and the
+  worst: musil is **hard-wrapped** (median line 69, max 179) while every other source is
+  paragraph-per-line (mauss 166, arendt 1273). A within-line matcher at a 120-char threshold
+  produces ~0 there **before the file is opened**. Two fabricated zeros, not one —
+  `after-the-reply-i` (max line 99) likewise. (2) The FID correction below.
+- **Score on that instrument today: five defects.** ASCII-blind (43% undercount, 3 sources
+  invisible, both positive controls in the same convention so neither could see it) · a negative
+  control passing for the wrong reason · a control aimed one layer below its gate · hard-wrap
+  blindness · and the FIX for hard-wrap classified mauss as hard-wrapped and failed both controls.
+  ⚠ **Only the fifth was caught by the instrument's own controls.** Three by my own re-checking,
+  **one by the steward**, and that one was the most serious.
+- **⚠ AND THE FIX IS A TWO-VALUED DETECTOR OVER A THREE-CASE STATE** (paragraph-per-line ·
+  hard-wrapped · **mixed** — after-the-reply ii/iii/iv/v have medians 30–63 with a few long
+  lines). **Third instance of that exact shape today**, after the wake digest's `wrap_inside`
+  alarm and the fleet's three-valued exit codes that already fixed it once (REVIEWED-104/108).
+  Left stating its limit rather than tuned until the limit stops being visible.
+
+- **Steward refuted my free-indirect-discourse argument, and the refutation is load-bearing.** I
+  argued fiction needs a *second fence mechanism* because FID and irony carry no delimiter. The
+  steward: in FID a reader takes the words to be Musil's, **rightly** — and a paraphrase is a
+  paraphrase; the fidelity of the meaning is what matters. Correct. **A PROVENANCE failure has a
+  second author who can be named and joined to** (Ranaipiri at L926); **a STANCE question has one
+  author and an interpretive judgment about endorsement** (FID, irony) — and irony proves it is
+  not a fiction matter at all, since Arendt reporting a view to demolish it raises the identical
+  question in non-fiction and nobody proposed a mechanism for that. I imported the second into the
+  first because a voice shift *felt* like the nested-voice class. **Consequence: (c) stays ONE
+  capability, not two** — fiction participates through marked dialogue like everything else
+  (musil carries 5014 opening quotes). The residue belongs to PENDING-134's whose-proposition
+  doctrine and to the synthesized tier's NLI, which was already built to ask about meaning rather
+  than ownership.
+
+## Confidence to recalibrate
+
+- **What the 32/36 result licenses is not yet settled.** It is the steward's judgment on
+  *relevance* over one run of one organ. Read as "the engine grounds at 11%" it would be a claim
+  about the engine; read as REVIEWED-114 intends, it is the fixture V4 is built to catch. I have
+  not established which framing the placed record supports — flagged rather than assumed.
+- Everything above the thread-validity gate was read from files this wake. Nothing in the
+  briefing is inherited from an unverified summary, but the 08-12 session's content is
+  **unestablished** — its transcript is on disk and unread.
+
+## Authorization moves
+
+- **REVIEWED-118 EXECUTED** (`e51e30d`). Steward-directed this session; the ruling was placed
+  2026-08-10 and had not been executed. Scope honoured exactly: retraction only. Every stated
+  exclusion held — ratio NOT re-derived (VOID pending PENDING-134), L926 NOT marked, instance 8
+  NOT dispositioned. Verification the ruling named: both files parse; fleet 8 suites / 263 checks
+  green (pre-commit hook ran it independently); reporter selftest PASS, live control 48 regions
+  non-empty.
+
+- **⚠ TWO THINGS OWED TO THE STEWARD, neither resolved by the executor.**
+  1. **Denominator collision.** REVIEWED-118 §3's "fr distinct spans 11 to 10" is arithmetic on a
+     headline field that counted LISTED spans (1 A + 9 B + 1 already-reclassified-out), not
+     grounded ones. The authorized number is written and the fields no longer sum to it — 11
+     listed, 9 grounded. Whether `distinct_spans` names the listed or the grounded population is
+     pre-existing and this entry did not address it. Same class as the finding-3 census corrected
+     at `546f316`. Recorded in the file, not settled.
+  2. **The reporter's region count did not shrink** (48 → 48), because the span was marked in
+     place rather than deleted. REVIEWED-118's parenthetical anticipated a shrink ("a retraction
+     shrinks exactly the thing that control reads"). The check it actually asked for — live
+     control loads non-empty — passes. Stated rather than allowed to read as agreement.
+
+## Sub-agent dialogues
+
+## Bypasses