[FIX] §9 dead text struck; PENDING-159 amended with the jurist's correction

The item's loudest claim was wrong: §9 does not MANDATE the provenance loss PENDING-153
recorded. Thistleweld's provenance was lost because nobody thought to record it; §9
mandates only that the claim be the steward's, and never addressed provenance either
way. An omission being discovered, not a rule doing damage — which changes the remedy
from amending §9 to clarifying it. Left visible rather than rewritten.

Option 3 closed, and on better grounds than the item offered: not §11's shared
formation, but that a jurist reading his output would ADJUDICATE it, collapsing the
position into a fourth checker. 'The steward's judgement not to relay is not a
bottleneck; it's the mechanism' — the item had treated it as a limitation.

Option 2's unnamed cost recorded: a 'from outside' flag is itself a signal the reader
responds to, so it does not preserve provenance neutrally.

⚠ Nothing built for the jurist view, deliberately: a marker with an implementation is a
channel, and a channel is option 3 by the back door. Noted because the executor's reflex
on reading it was to reach for a script.

§9's 'executor or jurist yields the floor' struck to 'executor' per the jurist on their
own draft — dead text, since there is no floor to yield where the fool cannot speak.

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

claude/governance/fool/TARBUCKLE-SPEC-13.1-2026-08-25.md

@@ -28,6 +28,10 @@ contact with the substrate; a spec written first would have carried all four.
 | **mumble** | wall clock, 20 min | status line, 120 s | `+ scripts/tarbuckle-mumble.py` |
 | **voice** | wake seam | SessionStart hook output | `scripts/tarbuckle-seam.py` |
 | **invoked** | the steward calls him by name | stdout, run by the steward | `scripts/tarbuckle-invoke.py` |
+| **voice** | wrap seam | `Stop` hook `systemMessage` | `scripts/tarbuckle-wrap.py` |
+
+Called by `! tarbuckle` (`bin/tarbuckle`, on PATH): bare or with a question; `mute`,
+`off`, `on`, `status`.
 
 Configuration, in `~/.claude/settings.json`:
 
@@ -158,10 +162,16 @@ whether he could be invoked — a question the document should have answered. **
 negative state-claim to go wrong in two days, and the second inside a document written to
 prevent exactly that.** Recorded rather than silently corrected.
 
-- **`mute` / `off`** (§9, *"available at all times"*) — **not built.** The only off-switch
-  is §9 below, which is removal, not muting. Muting is never a fault and there is
-  currently no way to do it.
-- **The wrap seam** (§4) — no delivery surface; route is a skill change.
+- ~~**`mute` / `off`**~~ — **BUILT** 2026-08-25. `! tarbuckle mute` silences the
+  utterance and leaves the body in the room; `! tarbuckle off` removes him;
+  `! tarbuckle on` returns. **mute ≠ off**: collapsing them would delete the visible
+  silence §8a exists to produce.
+- ~~**The wrap seam**~~ — **BUILT** 2026-08-25 on `Stop` + `systemMessage`, gated on an
+  actual `/wrap-up` invocation detected structurally in the transcript. `SessionEnd`
+  remains unusable and the reason stands in §4.
+- **PENDING-159** — the fool cannot reach the jurist, and what does reach him arrives
+  without provenance. `[ESCALATE]`, jurist view received: option 2 narrowly, optional,
+  **and deliberately unimplemented** — a marker with an implementation is a channel.
 - **The two-week rate report** — §8 obliges it; `DEFERRED-DECISION: mumble-rate-two-week-report`,
   converted `manual` → `date 2026-09-08` the day the body shipped.
 - **Frequency remains UNKNOWN** and is not guessed. The invocation log now measures the