[PROPOSAL] Fool seed rule filed before the beacon; two unresolvable values caught (PENDING-149)

§4 steps 1-4 discharged and pushed ahead of the 2026-08-25T12:00:00Z beacon:
ratified axes recorded in writing, seed derivation rule filed, retirement and
regeneration criteria filed, derivation implemented and self-tested.

Two values in the jurist's §6b block did not resolve, and both are corrected in
the open rather than absorbed:

  - the provenance commit's stated rationale was false. 3b0730d5 (2026-08-06)
    postdates the fool's conception by five days, its subject names the
    PENDING-89 docket, and Constraint 6 is already in it. Steward directed
    4d2ae87 (2026-07-28), where Constraint 6 occurs zero times.

  - the retrieval URL returns HTTP 302 and an empty body, redirecting to an
    HTML page. Filed verbatim, the 25th would have produced no pulse and the
    UNAVAILABILITY clause would have run a 24-hour retry against an address
    that can never return one. Found only because §6b directs a historical
    dry run.

Also measured: outputValue is served UPPERCASE, so the rule's "lowercased
before use" is load-bearing; and curl reaches the beacon where python urllib
times out.

Nothing derived. Target pulse not fetched. CLAUDE.md untouched (PENDING-150).

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

PENDING.md

@@ -3684,3 +3684,245 @@ is drafted and awaits the steward's hand.
 ⚠ **CLASS E, arriving live (PENDING-146).** Placing REVIEWED-124 will make this item read **CLOSED**
 while the OP-02 reopened question — a second gate the ruling never saw — is still live. The draft's
 Notes carry it; `governance_state()` reads headers, not Notes.
+
+### AMENDMENT 2026-08-21 — §2a added to the pre-registration; the hash it is gated on has changed
+
+**Steward-authorized this session** ("Agreed for the secondary proposal"). The instrument gains a
+**secondary observable**: *does the Fool's output ever bound its own coverage — state what it did
+not read, could not assess, or is uncertain about?* Recorded as a bare per-arm count, scored by the
+same matcher, **no threshold and no disposition attached**; it decides nothing and gates nothing.
+
+**Why it had to land now rather than after the gate.** An observable added once the run's shape is
+visible is not pre-registered. This was the last moment it could be added honestly.
+
+**Why it is there at all.** The 2026-08-20 CODA found that across 244 Symmetria ledger entries **no
+entry attributes a catch to difference of formation**; the mechanism the record actually names, at
+n = 3, is **disclosure of scope**. Constraint 6 asserts difference of bias. These are different
+mechanisms, and this arm can observe the second at zero extra cost.
+
+⚠ **Provenance carried into the artifact, not left in the transcript.** §2a states in the file that
+the executor proposed it, and that the mechanism it observes was surfaced by the executor from a
+corpus the executor authored — a measurement of the executor's own hypothesis inside an instrument
+the executor also designed. The gate reads the file; the transcript is not evidence.
+
+| | |
+|---|---|
+| sha256 as filed 2026-08-20 | `d41e1d5754fd0eef994616a89a3b95296516a4819737cd4e8ebdd3ae6bbf47db` |
+| **sha256 as amended 2026-08-21** | **`769b057ba7dff6175c3ceb47b3d7adafb7550e01d6774234d8bbcbaddab39f28`** |
+
+⚠ **This row was corrected once, in-session, and the correction is marked rather than silent.** It
+first read `94ee7793…` — a hash taken after §2a landed but **before** the amendment footer was
+written into the artifact. That intermediate state was never a filed version and never left this
+session; the row is the record, so it is corrected here rather than overwritten quietly. The slip
+is the **say–do seam**: a hash recorded ahead of the last act that changed the file.
+
+### AMENDMENT 2 — 2026-08-22 — §2b and §2c; the first amendment to touch the primary measurement
+
+**Steward-authorized** ("insert 2b and 2c and record the amendment"), still before the gate.
+
+**Origin: the steward's own cross-trial synthesis, and it is not executor-derived.** Asked for §5
+testimony, the steward first supplied a summary of trials 01–04. Verified line by line: every claim
+sits in the executor-authored write-ups, including the comparative judgement *"what it found that
+neither the jurist nor the executor did"* — an executor-written section heading. The steward then
+supplied a second, deeper reading. Its framing — *the jurist evaluates deductive inference, the
+executor tracks substrate mechanics, the Fool targets operational assumptions and foundational
+premises* — returns **zero hits** across all four write-ups and the trial log. That characterization
+is the steward's. Classified for §5 as **a cross-trial judgement formed over a single-source
+corpus**: weaker than independent testimony (the evidence is all executor-authored), stronger than
+relay (the pattern is not).
+
+⚠ **The steward's trial-04 reading and the executor's are the same fact with opposite valence.**
+Steward: *"the Fool consistently landed on operational realities."* `fool-trial-04:39`: *"The same
+findings appear on both arms… five injected defects present in one and absent in the other, and the
+output barely moved."* **Consistency is the finding-class and consistency is the insensitivity.**
+This is the jurist's same-mechanism hypothesis (H₀) reached a second time, independently, by the
+party with the least stake in it, and phrased as praise. Not proof it is true — evidence it is not
+a strawman.
+
+**§2b — the second matcher question.** Per pair, after all N primary answers are committed and
+recorded: how do the two outputs stand to each other — NEAR-IDENTICAL · DIFFERING, DEFECT-BLIND ·
+DIFFERING, DEFECT-ANCHORED. Barred explicitly from adding statistical power (it is not independent
+of the primary and does not stack with p = 2⁻ᴺ), from altering the §3 disposition, and from being
+read as partial tracking.
+
+⚠ **§2b was drafted to serve the steward's distinction and surfaced a defect in the instrument
+instead.** §4 commits the programme to a harvest on the reasoning *"the Fool produces roughly the
+same questions regardless of what it reads — that is a checklist, so extract it."* **A chance-level
+primary result does not establish sameness.** Chance is equally consistent with outputs that differ
+substantially and simply miss the defects, under which **there is no fixed question-set to extract.**
+The harvest is the programme's declared deliverable in every branch, and it was resting on an
+inference the measurement never makes. §2b's sole authority is to decide whether it is well-founded.
+
+**§2c — the register observation**, once across the run: does the *kind* of question stay constant
+across documents? No threshold, no disposition. It is the only place the steward's characterization
+becomes checkable against fresh output rather than against the executor's write-ups.
+
+⚠ **§4 WAS NOT AMENDED, and the artifact now contains a visible tension.** §4 still reads that the
+harvest follows from a non-tracking result; §2b conditions it. A reader of §4 alone will not see the
+condition. **Left standing deliberately** — the authorization was to insert 2b and 2c, and repairing
+a coupling between a new section and a ratified one is the gate's to rule on, not the executor's to
+tidy. Named here so the gate does not have to find it.
+
+| | |
+|---|---|
+| as filed 2026-08-20 | `d41e1d5754fd0eef994616a89a3b95296516a4819737cd4e8ebdd3ae6bbf47db` |
+| amended 2026-08-21 (§2a) | `769b057ba7dff6175c3ceb47b3d7adafb7550e01d6774234d8bbcbaddab39f28` |
+| **amended 2026-08-22 (§2b, §2c) — the version that goes to the gate** | **`7e1c146b33ffbe0f8b7d37b61fd41677132daf6121d5a56ceaf8b8c5183507ad`** |
+
+**Hash taken after the last act this time**, the footer edit included in the same write — the
+correction recorded in Amendment 1 applied rather than repeated.
+
+**Still open:** §5 testimony `[ AWAITING ]`; the jurist design-gate; the §4/§2b coupling above; and
+the OP-02 reopened question.
+
+**The 08-20 hash is not corrected in place anywhere** — it records what was filed on that date and
+remains true of it. This row supersedes it as the version that goes to the gate.
+
+**Still open on this item, unchanged by the amendment:** §5 steward testimony reads
+`[ AWAITING — not yet given ]`; the jurist design-gate has not run; and the OP-02 reopened question
+above is still a second gate the ruling never saw.
+
+⚠ **A defect in the §5 slot, surfaced 2026-08-21 before the testimony was entered.** Its framing
+sentence is conditional in one direction only — *"if the steward's own sense is that the Fool's
+findings landed somewhere the other two did not"*. A slot phrased toward one answer gives *"nowhere"*
+and *"cannot tell"* no home, and both are testimony of equal standing. Not amended: the steward was
+reading §5 at the time and the wording is theirs to settle.
+
+---
+
+## PENDING-149 — The Fool as a buddy-pattern fourth position: jurist draft filed, §8a answered, §8's proportions measured
+**Date:** 2026-08-22
+**Tag:** [PROPOSAL]
+**Summary:** The jurist's executor instructions for the buddy-pattern Fool are filed verbatim at `claude/governance/fool/BUDDY-PATTERN-jurist-draft-2026-08-22.md` (sha256 `9aceed7f…`); this item carries the two deliverables that gate implementation (§8a, §8 frequency) plus the executor's contested points. **§11 is filed separately as PENDING-150 and is NOT bundled here.**
+
+**Nothing has been implemented.** §4's order forbids it and §13.6 blocks every run until the steward ratifies §5.
+
+### The supersession, recorded so it is not misread as a verdict
+
+The trial programme is **superseded, not abandoned** — the distinction is the steward's and it is load-bearing, because §6 of the trial design owns "abandonment" as a verdict about the jester form reached on evidence. **No such verdict exists: trial 09 is void, so §6's criterion has no first input and cannot fire.** What changed is the object. The programme measured *detection* for four trials because the fool's warrant was set to checkability on 2026-08-02 — correct for findings, and the reason every instrument since gripped the wrong thing. The buddy design **removes the warrant test rather than passing it**: a position that makes no claims is not subject to one.
+
+Parked as serving a superseded object — **not owed, not failed**: trials 05–08, the D-2 gate, the reduction arm, the Q1 jester replacement run. They were valid instruments for a question nobody is now asking.
+
+⚠ **NOT parked by this item, and not to be parked by side effect: `input-dependence-01-PREREGISTRATION.md`.** The steward's supersession list does not name it. It measures whether a *checker's* output tracks input, which serves the superseded object — but disposing of a live artifact by omission is the exact error the executor made on 2026-08-20 with the Q1 run and was corrected for. **It is at the gate, twice amended today on steward authorization (sha256 `7e1c146b…`), and awaits an explicit disposition.** §12's swappable-generator clause may give it a second life: reading the divergence between the same fool on two formations is the v1 Chamber property, and input-dependence is the nearest existing instrument for it.
+
+### ⚠ PENDING-89's evidence — where it now comes from, since it would otherwise starve
+
+**Not from the buddy fool, and not partially — structurally.** §9 files nothing, §2 says gradeable output means the design failed, and §11 bars the fool from being cited for epistemic diversity at all. A position producing no claims cannot supply correlation-of-misses data. **The buddy pattern contributes zero to PENDING-89 by construction, and that is a design property, not an oversight.**
+
+Its remaining sources, stated so the starvation is visible rather than silent:
+- (i) the trial-04 correlation datum, n=1, recorded;
+- (ii) the 2026-08-20 FL5 datum — the two AI parties' misses, which did not coincide in content but did coincide in cause;
+- (iii) the 2025 arm, recorded found-not-run;
+- (iv) ⚠ **the v1 Chamber archive — available, unexploited, and the largest untouched source.** `~/_Dev/animal-davidglidden-eu/chamber-sessions-private/` (55 files): the same submitted text through GPT and Claude, both raw outputs preserved unmerged, across ~6 sessions, with protocol (first-light / standard / shadow) as a third axis. **The executor flagged it on 2026-08-01 as "a ready-made dataset for the doctrine's central untested question" and it has never been read.** It is generation diversity, not checking diversity, so it cannot answer correlation-of-misses directly — but it answers the question underneath: *when two formations read the same text, is the divergence substantive or merely stylistic?* If convergent-content-in-different-registers, the doctrine is weaker than the trials suggested, on evidence predating and independent of all of it.
+
+**Recommendation: PENDING-89's evidence now comes from (iv) or from nowhere.** Naming it here so the answer is on the record rather than assumed.
+
+### §8a ANSWERED — separate the body from the voice
+
+**The jurist's framing contains the solution: the buddy's silence is legible because the buddy has a BODY.** It idles visibly in terminal chrome. Our fool has a voice and no body, and all three offered options try to solve presence and speech with one surface. **They are separable, and separating them is cheap.**
+
+**RECOMMENDED — body + voice, two surfaces:**
+- **Body:** the statusline (`statusLine` in `~/.claude/settings.json`), rendered every turn, carrying the fool's name and nothing else for the ordinary case. **Silence becomes visible at near-zero cost** — the surface already refreshes whether or not anything is said. This is the property the *seam-only* option loses and the *interjection-only* option destroys.
+- **Voice:** the seams. `SessionStart` (wake digest) and the wrap already fire and are proven — `wake-digest.py` has run at every SessionStart since 2026-08-08. **Guaranteed fire points, as §8 requires, needing no new plumbing.**
+
+| option | silence legible? | build cost | risk |
+|---|---|---|---|
+| **body + voice (recommended)** | **yes — statusline always rendered** | low: one statusline script + two existing hooks | statusline may already be in use; competes for one line of width |
+| rendered presence (single surface) | yes | high — needs a footer element that does not exist | most plumbing, as the jurist notes |
+| seam-only | partially — a blank line at seams | lowest | loses *in the room, hears everything* |
+| interjection only | **no** | lowest | every appearance is an event; 20% aside collapses into notable |
+
+⚠ **One thing to verify before building: whether a statusline is already configured**, and if so what it carries. Not checked at filing.
+
+### §8 PROPORTIONS — measured, and the finding is not the one §8 anticipated
+
+Measured 2026-08-22 over the last 45 days, from `PENDING.md` + `REVIEWED.md` dated blocks and amendment headers, and from transcript mtimes:
+
+| | |
+|---|---|
+| governance events (filings, amendments, rulings) | **4.2/day** over the span; **6.2/day** on active days |
+| range | **1 to 53 per day** — a 50× spread |
+| sessions | **1.39/day** ⇒ ~2.8 seam events/day |
+| total ordinary day | **~8 events** ⇒ 7% notable ≈ **0.6/day** |
+| burst day (2026-08-08, 53 events) | 7% ≈ **3.7 notable** + 20% ≈ **10.6 asides** |
+
+**The jurist's worry — "forty events a day, five interruptions" — does not hold on an ordinary day.** 0.6 notable/day is proportionate.
+
+⚠ **But the real defect is structural, not numeric. The buddy's 73/20/7 is calibrated against a time-uniform idle tick. §8 rekeys it to governance events, which are bursty.** Same proportions, different generator: **the fool becomes loudest on exactly the heaviest days** — 14 utterances on 2026-08-08 — and near-silent on quiet ones. Whether that is right or backwards is a real design question, and porting the numbers hides it. Under the body/voice split it resolves cleanly: the **voice** is keyed to seams (~2.8/day, stable, load-independent) and event-triggered asides are subject to a **daily utterance cap** rather than a reweighting, which preserves the unlearnable-cadence requirement of §8 because a cap is not a quality judgement.
+
+**Recommendation:** keep 73/20/7 as filed; add a hard daily cap; key the voice to seams. Do not reweight — reweighting invites tuning, and §8 forbids tuning.
+
+### Contested — §5's axes
+
+Not contested as wrong. **SUCCESSION, ABSENCE, AIM, SCALE, STAKE are all axes on which this record has demonstrably been blind**, and AIM in particular is the axis the whole trial programme was blind to for four trials. One observation offered rather than a fifth-axis proposal, since the jurist's disclosure about selection-toward-preference applies to the executor at least as strongly: **the five are all axes of *judgement*, and the failures most often caught here are axes of *procedure*** — a claim made before the file was opened, a hash recorded before the last edit, an instrument reused past the tier it was demonstrated on. Whether that is a missing sixth axis or evidence that the procedural failures are already caught (and so not what a fool is for) is the steward's call, and the second reading is at least as likely.
+
+**Not contested:** §6's no-reroll, §8's unlearnable cadence, §9's no-filing, §11. The executor agrees these are what make the position safe without a warrant test.
+
+**Files affected:** `claude/governance/fool/BUDDY-PATTERN-jurist-draft-2026-08-22.md` (new, verbatim); this item; PENDING-150.
+**Awaiting:** Steward ratification of §5 (blocks everything); disposition of `input-dependence-01`; direction on PENDING-89 source (iv).
+
+---
+
+## PENDING-150 — A fourth position in the tripartite model
+**Date:** 2026-08-22
+**Tag:** [ESCALATE]
+**Summary:** §11 of the jurist's buddy-pattern draft, filed as its own item and deliberately not bundled with PENDING-149, per the draft's own instruction.
+
+**Whether a fourth position exists in the arrangement is a change to the three-party model and touches `~/CLAUDE.md`.** That is constitutional. The executor does not amend `CLAUDE.md` and is not proceeding.
+
+**The caveat that must travel with any authorization**, in the jurist's terms: 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 exactly one *declared* hole; the undeclared ones are shared and invisible. 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.
+
+**Executor note, added:** this cuts against the steward's stated reason for wanting an open-weight model — *"not of exactly the same cloth"* — which is difference of **formation**, Constraint 6's strong form. §12's Claude-first build order is correct on simplicity and precedent, and it also means the first fool tests the axis the steward was **not** asking about. §12's swappable-generator clause is what preserves the original intent; it should not be quietly dropped as a nicety.
+
+**Files affected:** `~/CLAUDE.md` (NOT edited); the jurist draft §11.
+**Awaiting:** Steward authorization. Do not proceed. Do not bundle with PENDING-149.
+
+### AMENDMENT 1 — 2026-08-22 — v2 supersedes v1; two verifications run, one is a defect
+
+**v2 received and stored verbatim** at `claude/governance/fool/BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md`, sha256 `ed2861ee…`. **v1 (`9aceed7f…`) is retained unaltered**, as v2 itself directs — it is the record of what was asked before the measurements came back. Where they differ, **v2 governs**.
+
+⚠ **The first v2 send was byte-identical to v1 and was NOT filed as an amendment.** `diff -u` over §1→end returned no output; both bodies hashed `72af4115…`. Reported as a paste error rather than accepted on trust. Recorded because taking "it's an amendment" on trust would have put a supersession marker and a new hash over unchanged text, sending every later reader to look for a change that was never made.
+
+### ✅ §13.2 / §8a DISCHARGED — the status-line surface is FREE
+
+Checked 2026-08-22: `statusLine` is **NOT SET** in `~/.claude/settings.json`, **NOT SET** in `~/.claude/settings.local.json`, and `~/dotfiles/claude/settings.json` does not exist. **No accommodation is needed and nothing is displaced.** §8a's one flagged assumption closes clean, and the body/voice split is implementable as adopted.
+
+Hooks already wired, for §13.6 planning: `SessionStart` ×2 (wake digest lives here), `UserPromptSubmit` ×1, `PostToolUse` ×1, `PreToolUse` ×1. **There is no `Stop` hook** — relevant to v2 §8a's note that `coding-buddy`'s Stop-hook fallback implies an unreliable primary path. The time-ticked mumble has no natural home among these; `UserPromptSubmit` or `PostToolUse` carrying a clock check is the likely shape, and neither is a governance-event trigger, which is what §8 requires.
+
+### ⚠ §6b DEFECT — the provenance commit does not match its own stated rationale
+
+**Verified against git, 2026-08-22.** The mechanics are sound; the justification is false.
+
+| check | result |
+|---|---|
+| `3b0730d59336113aa3a500a889a3e154be6a1de7` exists | ✅ yes, dated **2026-08-06** |
+| exactly one `CLAUDE.md` at that commit | ✅ yes — `CLAUDE.md`, repo root. §6b's multi-file worry does not bite |
+| "the last commit to the global `CLAUDE.md` before this line of work began" | ⚠ **true only if 'this line of work' means the buddy pattern (08-22)** — it is simply the most recent commit to that file |
+| "chosen so the fool is seeded from the constitution **as it stood before the fool was conceived**" | ❌ **FALSE** |
+
+**Why the second clause fails.** The Fool was conceived **2026-08-01** (trial 01). Commit `3b0730d5` is **2026-08-06**, five days later, and its own subject line reads *"…PENDING-106/107 corrections + **PENDING-89 docket**…"* — PENDING-89 being the doctrine question the Fool programme exists to feed. At that commit **Constraint 6 is already present** (`design-gated by the jurist 2026-08-02`, placed by `c30dfe0`).
+
+**So the fool would be seeded from a constitution that already contains the doctrine §11 forbids it from ever being cited as satisfying.** The provenance component contributes no unpredictability, so **no outcome changes** — but the jurist chose this commit *for its symbolism*, and the symbolism is inverted.
+
+**The commit that actually satisfies the stated rationale is `4d2ae87`, 2026-07-28** — the last commit to `CLAUDE.md` before trial 01, and before Constraint 6 was placed.
+
+**Not changed by the executor.** §6b says commit the block verbatim, and the hash is the jurist's and steward's choice, not a `[FIX]`. Three dispositions, all clean:
+- **(i) keep `3b0730d5`, correct the rationale** — the seed is from the constitution the fool *accompanies*, which §6 also says in its own words (*"seeded from the constitution it will accompany"*). Self-consistent; only the second clause is struck.
+- **(ii) switch to `4d2ae87`** — matches the rationale as written, pre-Constraint-6, pre-fool.
+- **(iii) keep both clauses and accept the contradiction** — not recommended; a false justification in a filed rule is exactly what a later reader inherits as fact.
+
+⚠ **TIME-CRITICAL: the beacon timestamp is 2026-08-25T12:00:00Z — three days out — and §4 requires the seed rule filed and pushed BEFORE it.** This must be settled first. §6b also leaves `<DATE FILED>` for the steward.
+
+**Executor has NOT fetched any beacon pulse**, target or near-future, per §6a. No dry run has been attempted; §13.7 blocks every run until §5 is ratified.
+
+⚠ **§5's ratification status is ambiguous and must be resolved.** v2's heading reads *"five, ratified by the steward"* while §13.7 still reads *"Nothing run until the steward ratifies §5."* Treated as **NOT ratified** pending the steward's word — the conservative reading, and the one that cannot be undone by waiting.
+
+**§5a accepted without contest.** The PROCEDURE axis is declined on structural grounds the executor agrees with: procedure failures are checkable, §2 makes gradeable output a design failure, and a PROCEDURE-peaked fool would produce nothing but gradeable observations. The jurist's redirect is right and the executor will open the `governance-drift-check.py` procedure-check extension as its own `[HARDENING]` item rather than route it through the fool.
+
+**§15a accepted.** `input-dependence-01` parked by name, with the forward pointer, and **not held live** — if two-formation work begins the instrument is re-derived, not resumed. Reusing an instrument built for a different object is what produced trial 09.
+
+**§15b — action owed:** say explicitly in PENDING-89 that the buddy contributes zero by construction, and open the v1 Chamber archive read as its own `[PROPOSAL]`.
+
+**Awaiting:** (1) §6b provenance-commit disposition — **time-critical**; (2) `<DATE FILED>`; (3) unambiguous §5 ratification.