[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

claude/memory/MEMORY.md

@@ -71,13 +71,13 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.
 
 ## Active Session
-> 🔑 **PULLING THREAD — CLOSE THE FOOL.** Steward 2026-08-20: complete the Fool and the Obsidian work **before** the fence resumes. The Fool is now **one gate and two steward inputs** from runnable. **(1) Place REVIEWED-124** — drafted copy-paste-clean in the PENDING-148 package Addendum; trial 09's void is in the fool tree and trial log **but NOT in the register**, and a reframe over an unrecorded void is worse than no reframe. **(2) Enter §5's testimony** in `input-dependence-01-PREREGISTRATION.md` — reads `[ AWAITING ]`; the steward is the only party who has read all three outputs against the same documents, and recalled-after-a-result is not testimony. **(3) The pre-registration goes to the jurist's gate** (sha256 `d41e1d57…`). ⚠ Residual coupling: the executor authored the instrument whose result bears on its own recommendation — the gate is the only check on that.
+> 🔑 **PULLING THREAD — CLOSE THE FOOL.** Steward 2026-08-20: complete the Fool and the Obsidian work **before** the fence resumes. The Fool is now **one gate and two steward inputs** from runnable. ✅ **(1) REVIEWED-124 IS PLACED** (2026-08-20, `~/REVIEWED.md` L1929) — trial 09 void is in the register. ⚠ But its Q3 as placed carries the jurist's FL5 reading that OP-02 overturned the same evening; the correction is in PENDING.md and NOT in the register. **(2) Enter §5's testimony** in `input-dependence-01-PREREGISTRATION.md` — still reads `[ AWAITING ]`; the steward is the only party who has read all three outputs against the same documents, and recalled-after-a-result is not testimony. ⚠ **The §5 slot is phrased in ONE direction** (*"if your sense is that it landed somewhere the other two did not"*) — *nowhere* and *cannot tell* have no home in it; steward's to settle. ✅ **§2a added 2026-08-21** (steward-authorized, pre-gate): secondary observable — *does the Fool bound its own coverage?* — bare count, no threshold, no disposition. ✅ **§2b + §2c added 2026-08-22** (steward-authorized, pre-gate) — second matcher question (NEAR-IDENTICAL · DEFECT-BLIND · DEFECT-ANCHORED, asked only after all N primaries are locked) + the register observation. ⚠ **Drafting §2b surfaced that §4's harvest rested on an inference the measurement never makes** — chance-level matching does NOT establish sameness, so the declared deliverable could have been authorized on evidence that doesn't support it. ⚠ **§4 NOT amended — the artifact carries a visible §4/§2b tension, left for the gate deliberately.** ⚠ **The steward's cross-trial framing is HIS, not relayed** (zero hits across all 4 write-ups + log) — but his trial-04 reading and `fool-trial-04:39` are the same fact with opposite valence: *consistency is the finding-class AND the insensitivity* ⇒ H₀ reached independently by the party with least stake. **(3) The pre-registration goes to the jurist's gate** (sha256 **`7e1c146b…`**; 08-21 `769b057b…`; as-filed 08-20 `d41e1d57…`). ⚠ Residual coupling: the executor authored the instrument whose result bears on its own recommendation — the gate is the only check on that.
 > ⚠ **CLASS E ARRIVING LIVE — placing REVIEWED-124 makes PENDING-148 read CLOSED while the OP-02 question is live.** One id, two asks; `governance_state()` reads headers, not Notes. This is PENDING-146's defect in real time, on today's own item.
 > ⚠ **THE SUBSTRATE OVERRULED BOTH AI PARTIES.** OP-02 was openable — the jurist called it *"the only document neither of us can open"*; it is on disk, hash-verified. **FL5 argues from Bourdieu's shared field and *illusio*, NOT formation.** Constraint 6 asserts difference of **formation** — an axis FL5 never uses. So C6 neither states FL5 "more sharply" (executor) nor negates its three-party half (jurist). Corpus check, 11 docs: `bourdieu`/`habitus`/`illusio` **0**, `peirce` **0**, FL4 substance **0**, FL3 **1** — against the pre-run census's 16/20/24. **The census counted topic-adjacency and over-reported the leak the executor's own recommendation rested on.**
 > ⚠ **THIRD check-before-claiming instance in three days, and it is INSIDE the document reporting the second.** Part IV.a propagated an inherited claim without opening a file whose hash the same package quotes three sections earlier. **Propagation is the more dangerous form — an inherited claim arrives already looking checked.** The jurist said "two is worth watching" before this one was found.
 > 🎯 **THE FOOL IS RE-AIMED — deployment, not doctrine.** Steward's original intent: *what does a different model, local on the M4, add or subtract in the fool role?* The log's subject is the **doctrine**; almost the whole programme serves that instead. ⇒ capability confound **irrelevant to seating a named candidate** (but **NON-TRANSFERABLE** — does not answer "should there be a Fool seat"); **no sound control needed** (differential criterion). Jurist finding adopted: **add and subtract may be ONE mechanism**, so "seat it for the class, treat noise as cost" is incoherent and is withdrawn. Three dispositions fixed pre-run; **the harvest runs in every branch**. ⚠ Parkable: trials 05–08, D-2, reduction arm — **05–08 and D-2 have NEVER existed as documents anywhere.** NOT parkable: the Q1 replacement run (a live authorization).
 > ⏸ **BEHIND THE FOOL, by the steward's own sequencing:** the fence — **(A) MOVE 2** (25 line-addressable blockquote runs; closable in ONE SITTING, needs no ruling), **(C) MOVE 1** (fence the citation at emission, D-1, 532 spans, ADDENDUM 4's per-class control requirement), **(B) THE ANSWER KEY** (session-sized, gates PENDING-142; key it on `##` **BLOCKS** not ids — PENDING-146). Citation exposure behind PENDING-131 (c) live since 2026-08-10. And the **Obsidian capture** — ⚠ the daily-note backup must accrete **DURING** the session; a wrap-triggered backup inherits the wrap's failure mode, which is exactly what 2026-08-19 demonstrated.
-> ⚠ **REPORT AT EVERY WAKE (REVIEWED-123 cond. 2) — N-now = 47/84, and it WENT DOWN** (60 on 08-17, 61 on 08-18, 47 on 08-19). **A 30-DAY ROLLING WINDOW, not cumulative** — at ~1 session/day it converges to ~30, so **`transcripts 84` very likely never fires** and every "N remaining" report was a false countdown. Ladder FROZEN generally; 4 rows queued in PENDING-141. **PENDING-147 needs a steward/jurist decision.** ✅ Leg (i) discharged — 47 transcripts archived outside the pruned tree, 46/47 sha256-verified.
+> ⚠ **REPORT AT EVERY WAKE (REVIEWED-123 cond. 2) — N-now = 46/84.** ⚠ **COUNT WITH THE TRIGGER'S OWN GLOB, NOT `find`** — `TRANSCRIPTS.glob("*.jsonl")` is NON-recursive (`governance-drift-check.py:331`); `find` recurses into `subagents/` and over-counts (54 vs 46 on 2026-08-22, a false rise). Series: 60→61→47→46, still falling. **Earlier framing:** (60 on 08-17, 61 on 08-18, 47 on 08-19). **A 30-DAY ROLLING WINDOW, not cumulative** — at ~1 session/day it converges to ~30, so **`transcripts 84` very likely never fires** and every "N remaining" report was a false countdown. Ladder FROZEN generally; 4 rows queued in PENDING-141. **PENDING-147 needs a steward/jurist decision.** ✅ Leg (i) discharged — 47 transcripts archived outside the pruned tree, 46/47 sha256-verified.
 
 - [Session 2026-08-20 — the Fool was answering a different question](session-2026-08-20-the-fool-was-answering-a-different-question.md) — reconstructed the crashed 08-19 session, then re-aimed the Fool. ⚠ **That night's literal Q was TESTED AND RETIRED — it failed its own test** (244 ledger entries, all authored by the party being measured ⇒ self-report with extra steps; see the CODA + [[feedback-checkable-question-over-self-authored-corpus]]). **REPLACEMENT Q: how many corrections in the record name a DISCLOSED LIMIT as the cause?** — answerable from what entries literally say. Early: **n=3, and across 244 entries NOTHING attributes a catch to difference of formation.** Constraint 6's mechanism is *difference of bias*; the record's is *disclosure of scope*. ⚠ **OPEN, OFFERED NOT TAKEN: add a secondary observable to the pre-registration — does the Fool's output ever bound its own coverage? MUST go in BEFORE the jurist's gate.** · [08-19 — the vault got a spec](session-2026-08-19-the-vault-got-a-spec-the-links-were-already-broken.md) (RECONSTRUCTED, not wrapped) · [08-17 — the instruments audited themselves and lost](session-2026-08-17-the-instruments-audited-themselves-and-lost.md).