Jurist ruling on the soul: one non-deviation, one deviation ruled harmless

Ruled from §7's text against the procedure as described, WITHOUT reading the soul —
the jurist naming that reading it would be "reaching for it through a side door". The
executor had read it and recused itself; the jurist had not, and could rule. The
recusal was not ceremony: it is what left a party able to answer.

(i) The missing glosses: NOT an error and NOT a gap, and this INVERTS my framing. I
filed the omission as a finding — the correct input withheld. The ruling: the bones
are five names and five numbers; the glosses are §5's definitions, not bones. Supplying
them would have handed over an interpretation of what SUCCESSION 96 means and produced
a character organized around legibility-to-a-stranger — a stat read as a personality
trait, which §3 forbids reading backwards. The risk ran the OTHER way: including them
would have been the deviation. §4 REGENERATION is therefore not reached at all.

My original heading is left visible with the correction marked on top, not rewritten.
A record that silently corrects itself teaches the next reader nothing about how the
error was made.

(ii) The name as an input: a real deviation from "from the bones", ruled HARMLESS —
the name was itself bones-derived, one generation kept, so it added no information not
already downstream. Recorded as DEVIATION RULED HARMLESS and explicitly not as
compliance: compliance would erase both the fact that practice departed from text and
the fact that someone with authority looked at it.

(iii) The jurist attached a pattern — second time this week a filed instrument's
wording was narrower than the practice it governed. Recorded as their observation; the
first instance is not named and I do not guess at it.

(iv) Both go in the attestation, NOT as a [FIX] to §7. Amending a rule after it has
fired is what §5b exists to prevent, and §7 has now fired. §7 stands exactly as filed.

Also: §6's "no regeneration ruling" went false — THIRD such bullet in this programme,
this time inside the very section that names the pattern and was written hours earlier.
A negative-status list does not become durable by knowing it is fragile. n=3 in one day.

Soul block re-verified byte-intact after the edits.

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

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

@@ -72,7 +72,15 @@ Sample lines, at the rate of roughly one an hour:
 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 finding — the prompt omitted §5's ratified axis questions
+## 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
@@ -109,6 +117,68 @@ stipulation leans **backward** (whose grip, which teacher) where the filed quest
 **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."*
@@ -119,19 +189,14 @@ offer is attractive — the other fool is described as *"pettier, funnier"* —
 the clause exists. **Recorded as declined, so no later reader mistakes silence for
 oversight.**
 
-**The only door that is not shut is §4 REGENERATION**, which permits regeneration *"ONLY
+**The other door — §4 REGENERATION, on a *"demonstrable implementation error"* — is now
-on a demonstrable implementation error, verified against this filed rule."* So the live
+also shut.** The executor referred that question to the jurist rather than answer it, being
-question is narrow and is **not the executor's to answer**:
+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.
 
-> Is *"the prompt omitted the ratified axis questions, and the peak axis was therefore
+**Both doors closed. This file is the soul, permanently.** Not by default, not for want of
-> generated against a stipulated meaning"* a **demonstrable implementation error against
+a ruling — by a ruling, on the text, from the party that had not read it.
-> the filed rule** — or is it within §7, which says only *"from the bones"* and does not
-> require the axis glosses to be supplied?
-
-⚠ **The executor states its interest and stops.** It is not neutral here: it read this
-soul, and a party that has read the output is the wrong party to rule on whether the
-output may be redrawn. **Jurist question.** Until it is ruled, this file stands as the
-soul, and §7 governs.
 
 ## 6 · What has NOT happened
 
@@ -142,4 +207,14 @@ both went false within hours of being written and neither was caught by any mech
 - §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.**
-- No second generation. No hand edit. No regeneration ruling.
+- 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.