dotfiles/claude/governance/fool/BUDDY-PATTERN-jurist-draft-2026-08-22.md

name, description, metadata

name	description	metadata
BUDDY-PATTERN-jurist-draft-2026-08-22	Jurist draft, 2026-08-22 — executor instructions for the Fool as a buddy-pattern fourth position. NOT AUTHORIZED. Filed verbatim as received; PENDING-149 ([PROPOSAL]) and PENDING-150 ([ESCALATE], §11 only) carry the executor's response. Supersedes the trial programme's object, not its record.	node_type type provenance governance-artifact reference Received from the jurist via the steward, 2026-08-22. Stored verbatim. Executor commentary lives in PENDING, never in this file.

Executor instructions — the Fool (buddy pattern)

STORED VERBATIM AS RECEIVED. Nothing in this file is executor-authored. The executor's contested points, the §8a answer and the §8 frequency measurement are filed under PENDING-149; §11 is filed separately under PENDING-150 and must not be bundled with it.

Prepared by the jurist, 2026-08-22, at the steward's request. Not authorized. File as [PROPOSAL]; see §11 for the part that is [ESCALATE] and must not be bundled with it.

---

1 · What this is

A fourth position in the working cycle, built on the Claude Code /buddy architecture. Ambient, event-triggered, one line at a time, addressed to the steward alone. It produces no findings, opens no items, and no ruling turns on it.

It is safe without being checkable, because nothing follows from it. This inverts the standing correction of 2026-08-02 — findings earn a hearing by being checkable, never by role — which is correct for findings and inapplicable here: a position that makes no claims is not subject to a warrant test. Do not build a checkability gate into this.

2 · What it is NOT

• Not a checker, auditor, reviewer, or devil's advocate. If its output can be graded, the design has failed.
• Not the Fool trial programme. Trials 01–09 measured a checker; this is a different object. Do not reuse their instruments, grading vocabulary, corpus, partitioning, or ground truth.
• Not an answer to Constraint 6. See §11.

3 · Reference implementation — scope limited

Reference: https://github.com/milind-soni/claude-pets — a third-party extraction of Claude Code's buddy system.

TAKE:

• the derivation chain (FNV-1a → Mulberry32 → stat draws, peak/dump assignment);
• the idle cadence table and its proportions;
• the fresh-overrides-stored rule.

DO NOT TAKE: species, rarity tiers, shiny, hats, eyes, sprites, animation frames, petting, the canned reaction strings, or the buddy's own stat set (DEBUGGING / PATIENCE / CHAOS / WISDOM / SNARK — superseded by §5).

⚠ Rarity in particular is a gacha mechanic: it scales stat FLOORS. A floor softens the dump, and the dump is the entire point. Do not port it.

Provenance: third-party extraction, not Anthropic documentation. Verify the derivation behaves as described rather than trusting the README. Once the seed rule is filed under §4, the filed rule governs — a quirk in someone's extraction must not become constitutional by accident.

4 · Pre-registration order — MANDATORY

The order is load-bearing. Each step is committed and pushed before the next begins.

1. Perception axes ratified by the steward (§5).
2. Seed derivation rule filed, naming a future timestamp (§6).
3. Abandonment criterion filed (§10).
4. Regeneration criterion filed (§10).
5. Timestamp passes; seed computed; bones derived.
6. Soul generated once from the bones (§7).

Steps 1–4 must be complete and pushed before step 5. Axes chosen after the seed is known, or with a fool in hand, smuggle the selection one level up.

5 · Perception axes — jurist proposal, steward ratifies

Five axes on 0–100. Each is something the fool could be blind to. The steward must be able to imagine a dump on any one costing him something; if not, it is not a real axis and should be replaced before ratification.

• 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?

Jurist note, disclosed: the steward has said his prior buddy was strong on pattern recognition and debugging. No axis above is drawn from that, on purpose. Adding one now would be selection toward a known preference.

Register properties — terseness, snark, obliquity, chaos — are NOT axes. They belong to the soul (§7) and are not seeded independently. The dump must be a blind spot, not a style: a fool that is merely predictable is blind to nothing.

6 · Bones

• Seed: SHA-256 of a public value that does not exist at filing time. The steward names the source and timestamp — NIST Randomness Beacon or equivalent.
• Derivation: seed → FNV-1a → Mulberry32 → stat draws.
• One peak (near max), one dump (near floor), three scattered.
• Recomputed fresh every session from the seed. Never cached. A stored value that disagrees with the fresh computation loses.
• No rerolls. The first output is the fool.

The dump stat is the point, not a side effect. It is the only guaranteed difference this position has, and the seed — not the steward — decides where the hole goes. Do not add a floor that softens it.

7 · Soul

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

8 · Cadence and triggers

Fixed table, adapted from the buddy's idle cycle: approximately 73% silent, 20% brief aside, 7% notable. Hardcoded. Neither the fool nor the steward can tune it.

⚠ Rationale, and this is the part most likely to be lost in implementation: a fool that decides when to escalate will learn from being heard or muted and drift toward speaking when it expects attention. That is the contamination gradient arriving through the one position built to resist it. The cadence must be unlearnable.

Triggers are EVENT-keyed, never content-keyed. It fires on occurrences — item filed, ruling recorded, proposal amended, census run, wake, wrap-up — and never on an assessment of whether the thing is any good. Do not implement quality evaluation of any kind.

Wake and wrap-up are guaranteed fire points. Observed drift consolidates at session seams, not at gates.

⚠ Sanity-check the proportions against real event frequency before implementing. If the cycle fires forty events a day, 7% notable is five interruptions and too many. Report the actual rate and propose adjusted proportions rather than porting the buddy's numbers blind.

8a · OPEN — where silence is legible

The buddy's cadence depends on a persistent rendered presence: it sits in a terminal chrome and idles visibly, so its silence is seen. This arrangement has no equivalent surface, and the fool has nowhere to idle.

Executor to propose how the fool is present when it is NOT speaking, with options and costs, before the cadence is implemented. Three shapes are known to the jurist and are offered as a starting point, not a menu:

• Rendered presence — a statusline or session-footer element, present always, mostly showing nothing. Closest to the buddy; preserves visible silence; most plumbing.
• Interjection only — appears when it fires, otherwise invisible. Cheapest. But every appearance becomes an event, which collapses the 20% aside into something that reads as notable.
• Seam-only — appears in the wake digest and wrap-up, always, sometimes with nothing to say. Silence becomes a blank line in a place already read. Nearly free, since both hooks exist — but loses the in the room, hears everything property.

⚠ If silence cannot be made legible, the three-state cadence collapses to two, and §8's proportions need re-deriving rather than porting. Do not implement §8 until this is answered.

The executor is better placed than the jurist to answer this — it knows the surfaces. Answer with options, not a decision.

9 · Channel and register

• Output reaches the steward. Filed nowhere. No PENDING entry, no log, no item.
• 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.
• mute / off available at all times. Mute rate may be counted; muting is never a fault.

Anything the steward carries into the record enters as the steward's, in his words. The fool is never cited as a source.

10 · Pre-registered criteria — filed before the fool exists

REGENERATION is permitted ONLY on a demonstrable implementation error, verified against the filed derivation rule. Not because the output is disliked.

RETIREMENT only on mechanical failure: does not fire; fires constantly; or produces gradeable in-genre findings despite §9.

NOT grounds for retirement: being uncomfortable, being frequently wrong, being annoying, being ignored. Those are the specification. Lear ignores his Fool for four acts and the Fool is not thereby broken.

11 · [ESCALATE] — do not bundle

Whether a fourth position exists in the arrangement is a change to the tripartite model and touches ~/CLAUDE.md. That is constitutional, and is a separate item requiring its own steward authorization. Do not amend CLAUDE.md under this proposal.

Standing caveat, to be written into the fool's own doctrine at the outset: if the fool runs on Claude, three of four parties share formation, which makes Constraint 6's concession worse rather than better. The dump stat mandates ONE declared hole; the undeclared ones are shared and invisible — and if what the jurist misses, the executor misses, and the fool also misses, that is PENDING-89's falsifier firing quietly.

⚠ THE FOOL MAY NEVER BE CITED AS SATISFYING CONSTRAINT 6, OR AS SUPPLYING EPISTEMIC DIVERSITY. It tests positional difference — PENDING-140's third axis — not formation difference.

12 · Build order

Claude-first. Simpler, and the steward's own precedent ran on Claude.

The generator is a swappable parameter: running the same fool on a local model later, and reading the divergence between the two, is the v1 Chamber property at negligible cost. Do not build for that now; do not preclude it.

13 · Deliverables

1. Spec document in the governance tree, with a provenance header stating it derives from this jurist draft and naming what was changed.
2. Answer to §8a — options and costs — before §8 is implemented.
3. Filed axes, seed rule, abandonment and regeneration criteria — committed and pushed before the seed timestamp.
4. Derivation implementation: deterministic, fresh-overrides-stored, no reroll path.
5. Hook wiring for event triggers, wake and wrap-up guaranteed.
6. Nothing run until the steward ratifies §5.

14 · Expected pushback

The jurist expects the executor to contest at least two things, and should:

• whether the five axes in §5 are the right five — the executor has working context the jurist does not;
• whether §8's proportions survive contact with real event frequency.

Both are contestable on evidence. §6's no-reroll rule, §8's unlearnable cadence, §9's no-filing rule, and §11 are not — they are what make the position safe without a warrant test, and weakening any one of them returns this to a fourth reviewer.

---

Jurist draft. The steward authorizes; the executor implements. Nothing in this document is a ruling.