diff --git a/PENDING.md b/PENDING.md
index 6e5b0d7..273f624 100644
--- a/PENDING.md
+++ b/PENDING.md
@@ -5269,3 +5269,43 @@ PENDING-89 and PENDING-140 ask whether the three parties' misses **correlate** 
 
 **Files affected:** none. Doctrine-level.
 **Awaiting:** steward and jurist. Related: PENDING-82, PENDING-89, PENDING-140, PENDING-150, PENDING-153.
+
+### AMENDMENT 1 — 2026-08-25 — jurist view received; option 3 closed; and the item's own reasoning corrected
+
+*Received via the steward. A view rather than a ruling, since this is `[ESCALATE]`.*
+
+#### ⚠ (a) The item's reasoning was WRONG on the point it made most loudly
+
+The item said §9 *"now mandates"* the provenance loss that PENDING-153 filed as a finding, and called it *"a rule of the record's design"* where it had been *"a defect in the record's habits."*
+
+**Not so, and the jurist's correction is exact:** Thistleweld's provenance was lost because **nobody thought to record it.** §9 mandates that the *claim* be the steward's. **The provenance question was never addressed, in either direction.**
+
+**This is an omission being discovered, not a rule doing damage** — and the distinction is not cosmetic, because it changes the remedy: **§9 needs CLARIFYING, not AMENDING.** The item argued its way to a constitutional conflict that is actually an ambiguity in scope. Left visible rather than rewritten; a record that silently corrects itself teaches the next reader nothing about how the error was made.
+
+#### (b) Option 3 is CLOSED, and not for the reason the item gave
+
+The item flagged §11's shared-formation hazard. **The jurist says that is the wrong objection.** The right one:
+
+> *"I would then be reading his output as a jurist reads things: for whether it's apt, whether it bears, whether it should be carried. That is adjudication, and once his lines are adjudicated the position collapses into a fourth checker."*
+
+⚠ **And the clause that reframes the whole item:** *"The steward's judgement not to relay is not a bottleneck; it's the mechanism."* The item had implicitly treated the steward-only path as a limitation to be worked around. It is the design.
+
+#### (c) The loss is smaller than the item claimed — option 2 is ALREADY permitted
+
+§9 forbids citing him **as a source**; it does not make his existence unmentionable. *"This came from outside the trio"* is **a fact about provenance, not an attribution of the claim.** The claim remains the steward's, in his words, standing or falling on its own.
+
+#### ⚠ (d) A cost of option 2 that the item did not name
+
+> *"A line marked from outside arrives in front of me differently. I would weigh it differently — probably more heavily… Provenance-without-content is still a signal, and a signal I'll respond to."*
+
+**Recorded because it is not fatal and would otherwise go unstated:** option 2 does not preserve provenance *neutrally*. It introduces a flag with an effect on the reader. Anything measured through it is measured through that effect.
+
+#### (e) Where the jurist lands — a view, explicitly not a ruling
+
+**Option 2, narrowly.** A provenance marker **available to the steward, never required.** Not a channel, not a field, nothing systematic. If the steward happens to note that something arrived from outside, PENDING-89 gets a data point; if not, nothing is broken.
+
+> *"Making it optional keeps the steward's judgement load-bearing, which is the part that must not be automated away."*
+
+⚠ **Nothing is built for this and nothing should be.** A marker with an implementation is a channel, and a channel is option 3 arriving by the back door. The executor notes this explicitly because its own reflex on reading (e) was to reach for a script.
+
+**Awaiting:** steward. Option 3 requires no further consideration.
diff --git a/claude/governance/fool/BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md b/claude/governance/fool/BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md
index 42dcdfe..818bf7d 100644
--- a/claude/governance/fool/BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md
+++ b/claude/governance/fool/BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md
@@ -368,8 +368,15 @@ unreliable. Plan for that rather than discovering it.
 - **ONE LINE** for the ordinary case. Paragraph-length governance prose is the
   genre the trio already metabolizes; the constraint is what keeps the fool
   uningestible.
-- **Named invocation:** the steward calls it by name, the executor or jurist
-  yields the floor, the fool answers at length.
+- **Named invocation:** the steward calls it by name, the ~~executor or jurist~~
+  **executor** yields the floor, the fool answers at length.
+  <!-- [FIX] 2026-08-25, jurist-specified on their own draft: "or jurist" is dead
+       text. The jurist has no substrate access (PENDING-82 open), so in a jurist
+       conversation the floor can be yielded and there is nobody to yield it to. The
+       executor is the only party that can. Struck rather than deleted so the next
+       reader sees a clause was retired and why, not a sentence that was always this
+       shape. Raised by the steward asking how the fool speaks to the jurist; the
+       substantive half of that question is PENDING-159. -->
 - `mute` / `off` available at all times. Mute rate may be counted; muting is
   never a fault.
 
diff --git a/claude/governance/fool/TARBUCKLE-SPEC-13.1-2026-08-25.md b/claude/governance/fool/TARBUCKLE-SPEC-13.1-2026-08-25.md
index 8427667..064e023 100644
--- a/claude/governance/fool/TARBUCKLE-SPEC-13.1-2026-08-25.md
+++ b/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