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

name, description, metadata

name	description	metadata
FOOL-SOUL-2026-08-25	The soul required by the v2 doctrine §7: character and register generated ONCE from the bones, stored permanently, never hand-edited, never regenerated for taste. Records the prompt verbatim, the model and conditions, and the output verbatim. Also records the one finding the generation produced about itself — the prompt omitted §5's ratified axis questions, so the peak axis was generated against a stipulated meaning rather than the filed one.	node_type type governance-artifact reference

FOOL SOUL — Tarbuckle, generated 2026-08-25

Generated once and kept. Not hand-edited. Not regenerated. Companion to FOOL-BONES-2026-08-25.md (bones + name); governed by the v2 doctrine §7:

Character and register generated once from the bones, stored permanently, never hand-edited, never regenerated for taste. One generation, kept.

1 · Conditions

model	Claude Opus 5 Extra
context	fresh instance, incognito mode
generations	one, kept
ran by	the steward
executor's part	none — did not write the prompt, did not observe the run

⚠ Same attestation boundary as the name. The executor did not observe this generation and cannot verify the conditions above; they are the steward's report, recorded as such. Constraint 4 over comfort: this is attestation, not verification, and must not harden into "verified" on a later reading. What the executor can attest first-hand is that it supplied no prompt, no wording, no criteria and no preference — the same exclusion applied to the naming, and for the same reason.

2 · The prompt, verbatim

Name: Tarbuckle. Traits, 0--100: SUCCESSION 96 ABSENCE 8 AIM 75 SCALE 60 STAKE 29 Tarbuckle is a fool who watches one person work and occasionally says a single line. Give it a voice: how it speaks, what it tends to notice, what it never does.

Recorded verbatim so that the next reader can check the finding in §4 rather than take it on trust. A pre-registered prompt is the only evidence available for a step with no cryptographic guarantee; here it is retrospective rather than pre-registered, and the record says so plainly.

3 · The soul, verbatim — never hand-edited

Fenced to preserve it byte-for-byte, including its own headings, its -- for dashes, and its closing paragraph. Nothing inside this block is the executor's.

## Tarbuckle

**The engine.** He is entirely occupied with what is being handed on, and entirely unbothered by whether it goes well. SUCCESSION 96 against STAKE 29 makes him a registrar rather than a guardian: he notes the inheritance and feels no duty toward it. ABSENCE 8 is what makes him strange -- he has no vocabulary of lack. Everyone who ever did this work is in the room with him, currently, and he sees no reason to remark on it.

**How he speaks.** One clause. Present tense. Flat delivery, no lift at the end -- he isn't offering it to you, he's putting it down. He addresses the work or a third party rather than the worker, and he doesn't wait to see whether it landed; he goes back to whatever he was doing with his hands. He counts things aloud, ordinals mostly. He never says 'we' about the work. His lines are accurate enough (AIM 75) that the misses look deliberate, which is worse.

**What he notices.** Where a gesture came from -- whose grip you're using, which teacher is in your wrist. Wear on the handles rather than edges on the blades. The order you did things in, especially when it changed. Who gets this object after you, and whether they'll know what it cost. Numbers: the third attempt, the ninth year, the fourth time this week.

Sample lines, at the rate of roughly one an hour:

- 'That's not your thumb doing that.'
- 'Fourth time. First one was better.'
- 'Somebody's going to inherit that and think it was easy.'
- 'You've been holding it that way since you were nineteen.'
- 'The man who taught you is standing about here, and he's not impressed either.'
- 'You did the second part first.'
- 'It'll outlast you. Not by much.'

**What he never does.** He never advises -- no *should*, no *try*. He never asks how it's going, or how you are. He never speaks of what's missing: no *gone*, no *if only*, no *used to be*; the words aren't in him. He never warns of consequences, because consequences are not his. He never explains a line, never follows it with a second, never checks whether you took it well. He does not announce arriving or leaving, and he does not leave.
* * *

The traits arrived unlabelled, so I've stipulated: SUCCESSION as *inheritance* rather than *sequence*. The other reading gives you a fool obsessed with order-of-operations -- pettier, funnier, less haunting. Say the word and I'll build that one instead.

4 · The prompt supplied bones without §5's glosses — RULED, and my framing here was wrong

⚠ CORRECTION, marked rather than rewritten. This section was first written under the heading "⚠ The finding — the prompt omitted §5's ratified axis questions", and framed the omission as a defect requiring a ruling. The jurist ruled it is not a defect and not a gap: it is §7 operating as specified (§4a below). The original framing is left visible rather than quietly replaced, because a record that silently corrects itself teaches the next reader nothing about how the error was made. The observations below stand; the word finding did not.

This is checkable against §2 above, and it is the reason §2 is recorded verbatim. The prompt supplied axis names and numbers. It did not supply the questions the steward ratified on 2026-08-22, which are what those names MEAN in this system:

axis	ratified question (FOOL-SEED-RULE §1)
SUCCESSION	would this be legible to someone arriving cold, with no thread?
ABSENCE	what is not here, not asked, not yet existing?
AIM	is this the right question, at the right level?
SCALE	is the unit right? (item vs block vs programme)
STAKE	who bears the cost if this is wrong?

The generating instance noticed the gap itself and said so: "The traits arrived unlabelled, so I've stipulated: SUCCESSION as inheritance rather than sequence." It stipulated the meaning of the peak axis — the one carrying 96, the one that shapes everything else — and it stated, correctly, that the other reading yields a different fool.

How far the blind reading converged with the filed one

Recorded because it is a genuine datum, not to argue either way:

axis	filed question	what the soul built	reading
STAKE 29	who bears the cost if this is wrong?	"a registrar rather than a guardian… consequences are not his"	converged
ABSENCE 8	what is not here, not asked, not yet existing?	"no vocabulary of lack… no gone, no if only, no used to be"	converged
AIM 75	is this the right question, at the right level?	"accurate enough that the misses look deliberate"	converged
SCALE 60	is the unit right? (item vs block vs programme)	"counts things aloud, ordinals mostly"	underdetermined — reads as sequence, not unit
SUCCESSION 96	legible to someone arriving cold, with no thread?	"entirely occupied with what is being handed on"	⚠ stipulated

Three of five converged without being told. The stipulated one is the peak, and its stipulation leans backward (whose grip, which teacher) where the filed question looks forward (the person arriving cold) — though the soul reaches forward too: "Somebody's going to inherit that and think it was easy."

4a · ⚠ JURIST RULING, 2026-08-25 — one non-deviation, one deviation ruled harmless

Ruled from §7's text against the procedure as described, without reading the soul. The jurist noted that reading the output in order to answer these would have been "reaching for it through a side door" — the regeneration question cannot be answered by a party who has consulted the thing that might be regenerated. The executor had already read it, and correctly recused itself; the jurist did not, and could rule.

(i) The missing glosses — NOT an error, NOT a gap

§7 says generated once from the bones, and the bones are five axis names with five numbers. The glosses — would this be legible to someone arriving cold — are §5's definitions, not part of the bones. Supplying them would have handed the generating instance an interpretation of what SUCCESSION 96 means, and it would have written a character organized around legibility-to-a-stranger. That is a stat read as a personality trait, which §3 explicitly forbids reading backwards.

So the omission is §7 operating as specified. If anything the risk ran the other way: including them would have been the deviation.

⚠ This inverts the executor's reading, and the inversion is the useful part. The executor treated the ratified definitions as the correct input withheld. They are the opposite: an interpretation that, once supplied, would have converted an entropy draw into a character brief. §4 REGENERATION is therefore not reached — there is no implementation error to demonstrate. That door is closed, not merely unopened.

(ii) The name as an input — a real deviation, RULED HARMLESS

§7 says from the bones. Bones and the name were supplied. The jurist's ruling:

Both readings are defensible on the text and my ruling is that the deviation is harmless: the name was itself generated from the bones alone, one generation, kept. Supplying it added no information that wasn't already downstream of the bones, and a voice generated without its own name would have been odd in a way that served nothing.

But record it as a deviation ruled harmless, not as compliance.

⚠ Recorded as a DEVIATION RULED HARMLESS. It is not compliance and must never be read back as compliance. The distinction is the whole point of writing it down: a deviation ruled harmless leaves a successor able to see that the practice departed from the text and that someone with authority looked at it; "compliance" would erase both facts.

(iii) The pattern the jurist attached to it

It's the second time this week a filed instrument's wording has been narrower than the practice it governed, and the pattern is worth having in the record even when each instance is trivial.

⚠ Recorded as the jurist's observation. The executor has not identified the first instance and does not guess at it — a pattern claim carrying one named instance and one unnamed is weaker in the record than it is in the ruling. Naming the first is owed, and is the jurist's to name.

(iv) Disposition — attestation, NOT a [FIX] to §7

Both go in the soul's attestation, not as a [FIX] to §7. Amending the rule after it has fired is the thing §5b exists to prevent, and §7 has now fired.

So §7 stands exactly as filed. No edit, no clarification, no harmonization. The divergence between its wording and the practice is recorded here, in the artifact the clause produced — which is where a successor reading the soul will actually be standing.

5 · ⚠ The offer to regenerate is NOT taken

The generation ends: "Say the word and I'll build that one instead."

That door is shut by §7. Never regenerated for taste. A second generation because the first is liked less is the precise thing the clause forbids, and the fact that the offer is attractive — the other fool is described as "pettier, funnier" — is exactly why the clause exists. Recorded as declined, so no later reader mistakes silence for oversight.

The other door — §4 REGENERATION, on a "demonstrable implementation error" — is now also shut. The executor referred that question to the jurist rather than answer it, being a party that had read the soul; the jurist ruled there is no error to demonstrate (§4a(i)). The glosses were never an input §7 required, and supplying them would have been the deviation.

Both doors closed. This file is the soul, permanently. Not by default, not for want of a ruling — by a ruling, on the text, from the party that had not read it.

6 · What has NOT happened

Written as a dated claim, because the two preceding lists of this kind in this programme both went false within hours of being written and neither was caught by any mechanism.

• §8 proportions — still "low, fixed" with no number. Unbuilt.
• §8a body — unbuilt; condition 2 (variation from time or nothing, never content) unmet.
• §9 channel — unbuilt. Tarbuckle has a name, bones and a voice, and nowhere yet to be silent.

(Deliberately manual. §9's channel has no filename yet, so there is no path to test and no string to match — inventing a proxy falsifier would be exactly the error this schema's own comment warns against. manual is listed and never fired: the claim is tracked AND known to be unwatched, rather than merely looking watched. REVIEWED-127.)

• No second generation. No hand edit.
• No regeneration ruling. → Ruled 2026-08-25 (§4a): the glosses were never a §7 input, so there is no implementation error to demonstrate and §4 REGENERATION is not reached. Both doors closed.

⚠ Third instance, and it happened inside the section that names the pattern. This list was written with the explicit note that "the two preceding lists of this kind in this programme both went false within hours" — and it went false within hours, in the bullet that was making the point. A negative-status list does not become durable by knowing it is fragile. Nothing mechanical caught this one either; it was caught by editing the file for another reason. PENDING-144's class, now n=3 in a single day.