The fool is named Tarbuckle; the name recorded beside the bones with its provenance

Named by the steward from the bones, ratified by the jurist. Recorded in the same
file as the bones because the naming is the ONE step with no cryptographic guarantee
behind it: the beacon can be re-fetched by anyone and the seed recomputed from two
public values, but a name cannot be checked that way. The procedure is the only
evidence it was not steered, so the procedure is what gets written down.

Recorded as ATTESTATION, not as established fact. Fresh instance, bones only, one
generation kept, Thistleweld unread — these are the steward's words ratified by the
jurist. The executor did not observe the generation and cannot verify any row of
that table, and the record says so rather than laundering a report into a finding.

What the executor can attest first-hand is the part where it was the contamination
risk: it supplied no candidates, no criteria, no shortlist, no opinion, and knew the
peak was SUCCESSION when it could have offered them. That route was never opened.

Keeps the jurist's reasoning verbatim, because it ties the name to a structural
requirement rather than to taste: "Tarbuckle says" will never sit comfortably in a
PENDING entry, and §9's unfileability is eroded by prose habit rather than by
decision. A name that resists the citing sentence defends §9 where §9 actually breaks.

Also fixes §7's "the filed rule not edited", false since 5737d4d. That is the SECOND
what-has-NOT-happened bullet in this programme to go stale within hours, after the
filed rule's own §6. Neither was caught by a mechanism; both were caught by someone
reopening the file. A list of what has not happened is a claim with a short half-life.
Noted where it happened rather than filed as new — it is PENDING-144's class and
PENDING-144 is open.

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

claude/governance/fool/seed/FOOL-BONES-2026-08-25.md

@@ -1,6 +1,6 @@
 ---
 name: FOOL-BONES-2026-08-25
-description: "The derivation record required by FOOL-SEED-RULE.md EXECUTION: raw beacon value, seed string, SHA-256, resulting stats, and the commit hash of the filed rule. The derivation ran ONCE, on 2026-08-25, against the pulse the rule names. This file is the record, not the rule."
+description: "The derivation record required by FOOL-SEED-RULE.md EXECUTION: raw beacon value, seed string, SHA-256, resulting stats, and the commit hash of the filed rule. The derivation ran ONCE, on 2026-08-25, against the pulse the rule names. Also records the name — Tarbuckle — with the provenance of its generation, that being the one step with no cryptographic guarantee behind it. This file is the record, not the rule."
 metadata:
   node_type: governance-artifact
   type: reference
@@ -81,6 +81,58 @@ ranges were filed before the value was knowable; the axis assignment came from t
 pulse. That a fool sharpest on SUCCESSION and near-blind on ABSENCE is a legible outcome
 for this system is an observation about the reader, not evidence about the draw.
 
+## 3a · The name — **Tarbuckle**
+
+Named by the **steward**, 2026-08-25, from the bones. Ratified by the **jurist**:
+*"Tarbuckle it is."*
+
+### Provenance of the generation — attested by the steward, NOT verified by the executor
+
+⚠ **This is the one step in the whole procedure with no cryptographic guarantee behind
+it.** The beacon can be re-fetched by anyone and the seed recomputed from two public
+values; a name cannot be checked that way. **The procedure is therefore the only evidence
+the naming was not steered**, which is why it is recorded here in the same file as the
+bones rather than mentioned in passing.
+
+| property | as attested |
+|---|---|
+| context | **fresh instance** — no thread, no session history |
+| input | **the bones only**: SUCCESSION 96 · ABSENCE 8 · AIM 75 · SCALE 60 · STAKE 29 |
+| generations | **one**, and kept — no iterating for taste, no shortlist, no second pass |
+| Thistleweld | not read by the generating instance |
+
+⚠ **Recorded as attestation, not as established fact.** The executor did not observe the
+generation and cannot verify any row of that table. Constraint 4 requires the system to
+report its own limits, so: **these are the steward's words, ratified by the jurist, and
+the executor's confidence in them is exactly its confidence in the steward — which is not
+the same thing as verification, and must not be read as it later.**
+
+**What the executor CAN attest first-hand**, being the one party in a position to have
+contaminated this step: **it supplied no candidate names, no criteria, no shortlist, and
+no opinion.** It was told the name as a decision already taken by both other parties. The
+one contamination route available to it — offering names once the bones were known, when
+it already knew the peak was SUCCESSION — was never opened.
+
+### Why it was kept — the jurist's reasoning, preserved because it will be read later
+
+> Odd, pronounceable, says nothing about the stats, and slightly ridiculous in governance
+> prose — which is the point. *Tarbuckle says* will never sit comfortably in a `PENDING`
+> entry, and that discomfort is a feature: it keeps the fool from being cited as a source,
+> which §9 requires and prose habits erode.
+
+This ties the name to a **structural** requirement rather than to taste. §9 makes the fool
+unfileable — output reaches the steward, filed nowhere, no `PENDING` entry, no log — and
+§2 makes gradeable output a design failure. Those are clauses; **prose habit is what
+erodes clauses**, by degrees, in the direction of citing whatever is available. A name
+that resists the sentence *"as Tarbuckle notes"* defends §9 at the level where §9 actually
+gets broken.
+
+*(One property is worth naming for the successor who wonders whether it was chance:
+**the name encodes nothing about the draw.** Had it, the bones would be legible in every
+utterance, and a fool whose stats can be read off its name is gradeable by construction —
+which §2 forbids. The jurist named the property; the reading of why it matters is the
+executor's.)*
+
 ## 4 · Verification performed at execution time
 
 Every check below was **run now**, not relayed from the 2026-08-22 record.
@@ -130,9 +182,22 @@ one way only is how a successor learns that a gate was closed but never why.)*
 
 ## 7 · What has NOT happened
 
-- No soul generated. §8 (proportions — still *"low, fixed"* with no number), §8a (body
+- **No soul generated.** Character and register are still to be generated **once** from
-  design) and §9 remain unbuilt.
+  the bones *and the name*, under the same discipline: one generation, no iterating for
+  taste, and by an instance that has not been reading Thistleweld. §8 (proportions — still
+  *"low, fixed"* with no number), §8a (body design) and §9 remain unbuilt. Tarbuckle has
+  a name and a shape and nowhere yet to be silent.
 - No retry, no second pulse, no regeneration. §4 REGENERATION is untouched and remains
   available only on a demonstrable implementation error verified against the filed rule.
 - `~/CLAUDE.md` not touched (PENDING-150 remains unbundled).
-- The filed rule not edited.
+- ~~The filed rule not edited.~~ → **Edited 2026-08-25, after it fired**, per its own §5b:
+  the `abandonment` → `retirement` harmonization, §6 marked superseded in part, and a new
+  §7 logging every post-beacon edit. Commit `5737d4d`. **Nothing in the clauses that
+  governed the derivation was touched**, and that is checkable rather than asserted — see
+  the rule's §7.
+
+⚠ **Second bullet in this programme to go stale within hours of being written** (the
+first was the filed rule's own §6, falsified at 12:00Z by the act this file records). **A
+list of what has NOT happened is a claim with a short half-life**, and neither instance
+was caught by any mechanism — both were caught by someone happening to reopen the file.
+Noted here rather than filed as new: it is PENDING-144's class, and PENDING-144 is open.