[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).
 

claude/memory/session-ledger-2026-08-21.md

@@ -0,0 +1,166 @@
+---
+name: Session Ledger 2026-08-21
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-08-21
+
+## Returns
+
+## What held
+
+- 2026-08-21 wake — N-now **re-measured, not relayed**: 54 (was 47 on 08-19). The standing
+  REVIEWED-123 cond. 2 obligation is what produces the number; quoting yesterday's would have
+  hidden the direction of travel, as it did on 08-19 in reverse.
+- 2026-08-21 wake — REVIEWED-124 reported as placed only after opening `~/REVIEWED.md` at the
+  line, not from the digest's LAST RULINGS summary. The digest reads headers; the discrepancy
+  below is in the Notes.
+
+## Open horizons
+
+- ⚠ **REVIEWED-124's Q3, as placed, carries the jurist's FL5 reading** — *"Constraint 6 … affirms
+  the negation of its three-party component"* — which the OP-02 substrate check overturned the
+  same evening. The correction is in `~/PENDING.md` L3610 and **nowhere in `~/REVIEWED.md`**.
+  The register now holds a substrate-contradicted claim in a permanent ruling.
+  ⚠ Amending `~/REVIEWED.md` is `[ESCALATE]`, steward's hand — a jurist sign-off does not
+  authorize one. This is a proposal to draft, not an edit to make.
+- ⚠ **Class E live (PENDING-146):** PENDING-148 now reads CLOSED while the OP-02 reopened
+  question is a second gate the ruling never saw.
+- `~/dotfiles/REVIEWED.md` modified and **uncommitted/unpushed** — the placement has not reached
+  either remote. Not touched at wake (the wake reads; the push belongs to the wrap).
+- Fool run blockers unchanged: §5 testimony `[ AWAITING ]`; pre-registration sha256
+  `d41e1d57…` unchanged ⇒ not gated. The offered-not-taken secondary observable (*does the Fool
+  bound its own coverage?*) must land **before** the gate or it is chosen post-hoc.
+- PENDING-147 (ii)–(iv) awaiting steward decision; leg (i) discharged.
+
+## Confidence to recalibrate
+
+- Drift-pattern held from 08-20: **check-before-claiming, PROPAGATION form — third instance in
+  three days, the third inside the document reporting the second.** An inherited claim arrives
+  already looking checked. Today's register discrepancy was found by opening the file; it would
+  not have been found by reading the wake digest.
+
+## Authorization moves
+
+## Sub-agent dialogues
+
+## Bypasses
+
+---
+
+### Authorization moves — 2026-08-21
+
+- **Steward authorized §2a** (secondary observable) into `input-dependence-01-PREREGISTRATION.md`,
+  **before** the jurist gate. Inserted verbatim as presented, plus a provenance-and-exposure
+  paragraph carried into the artifact — the gate reads the file, not the transcript. Amendment and
+  both hashes recorded under PENDING-148.
+  - as filed 2026-08-20 · `d41e1d57…`  →  **as amended 2026-08-21 · `769b057b…`**
+- §5 testimony **not** touched — the steward was reading it; the wording is theirs.
+
+### Returns — 2026-08-21
+
+- ⚠ **Say–do seam, self-caught.** Wrote a hash into PENDING.md, then edited the artifact's footer,
+  which invalidated it. The intermediate `94ee7793…` never left the session but *was* in the
+  register for a few minutes. Corrected with the correction marked, not overwritten quietly.
+  **The rule violated is my own: record after the act, or mark the record prospective.**
+- ⚠ **Named before the steward wrote into it:** §5's testimony slot is conditional in one direction
+  only. A slot phrased toward one answer collects one answer. Surfaced rather than banked.
+
+### Authorization moves — 2026-08-22 (session continues past midnight)
+
+- **Steward authorized §2b + §2c** into the pre-registration, pre-gate. §2b is the **first
+  amendment to touch the primary measurement** rather than sit beside it.
+  - `769b057b…` → **`7e1c146b…`** (as-filed 08-20: `d41e1d57…`)
+- **Hash taken after the last act**, footer edit included in the same write — yesterday's say–do
+  seam applied rather than repeated.
+- **§4 deliberately NOT amended.** The authorization was to insert 2b and 2c. Repairing a coupling
+  between a new section and a ratified one is the gate's to rule on. Tension named in the artifact
+  footer and under PENDING-148 so the gate does not have to find it.
+
+### What held — 2026-08-22
+
+- **Checked the steward's material instead of accepting it.** First summary: every claim traced to
+  executor-authored write-ups, including the comparative judgement — which is a section heading I
+  wrote. Second, deeper synthesis: **zero hits** across all four write-ups and the log ⇒ genuinely
+  the steward's. Same discipline, opposite verdicts, both from grep rather than impression.
+- **Drafting an addition found a defect in the host.** §2b was asked for to serve the steward's
+  register distinction; it surfaced that §4's harvest — the programme's declared deliverable in
+  every branch — rested on sameness the measurement never establishes. Not what it was drafted for.
+
+### Open horizons — carried
+
+- ⚠ **§4 / §2b coupling** — for the jurist's gate.
+- ⚠ **§5 still `[ AWAITING ]`**, and its one-directional framing still unfixed (steward's to settle).
+- ⚠ **If the steward's sense of the Fool is largely executor-framed, "the Fool's added value" may be
+  partly the executor's write-up rhetoric rather than the model's output.** No arm of the programme
+  measures this. §2c is the closest thing — it checks the characterization against fresh output.
+
+### Returns — 2026-08-22, second batch
+
+- ⚠ **JURIST CORRECTION ACCEPTED, and it is the wrong-subject family again.** I concluded the
+  perturbation framing "had never been written down" and that "nothing of mine could have pushed
+  the steward toward it." **I searched three stores; there are four.** The observation exists in
+  Claude.app conversation history dated 2026-08-17 — the day trial 09 was designed — which no
+  instrument on my side can reach. **The negative had no positive control on the instrument's own
+  reach**, which is the epistemic standard this record already holds and which I was in the middle
+  of *performing* when I broke it. Checked: the overclaim never reached disk. The on-disk claims
+  are correctly scoped to "all four write-ups and the trial log" and stand.
+- ⚠ **SECOND INSTANCE, SAME FAMILY, FOUND IN THIS SESSION'S OWN WAKE REPORT. N-now is 46, not 54.**
+  I reported 54 under the standing REVIEWED-123 cond. 2 obligation, using `find` — which recurses
+  into `subagents/` and counted **9 subagent transcripts**. The trigger uses
+  `TRANSCRIPTS.glob("*.jsonl")`, verified non-recursive at `governance-drift-check.py:331`.
+  Series corrected: **60 → 61 → 47 → 46**, still falling. My 54 was the only rise and it was an
+  artifact of using a different instrument than the trigger. **The obligation was discharged with
+  the wrong tool, which is worse than not discharging it — it reported the trend backwards.**
+- Both instances share one shape: **the instrument's reach was not itself checked before its
+  silence was read as evidence.**
+
+### Authorization moves — 2026-08-22, second batch
+
+- **Jurist buddy-pattern draft filed verbatim** at `claude/governance/fool/BUDDY-PATTERN-jurist-draft-2026-08-22.md`
+  (sha256 `9aceed7f…`), provenance header stating nothing in it is executor-authored.
+- **PENDING-149 [PROPOSAL]** — §8a answered (body/voice split), §8 proportions measured, §5 axes
+  responded to, PENDING-89's evidence source named.
+- **PENDING-150 [ESCALATE]** — §11 alone, deliberately unbundled per the draft's own instruction.
+- **Nothing implemented.** §4's order and §13.6 block every run until the steward ratifies §5.
+
+### Open horizons — carried, 2026-08-22
+
+- ⚠ **`input-dependence-01` has NO disposition.** The supersession list does not name it. Not parked
+  by side effect — that is the 08-20 Q1 error and I was corrected for it once already.
+- ⚠ **PENDING-89 starves unless the v1 Chamber archive is read** — 55 files, flagged by me on
+  2026-08-01 as the ready-made dataset for the doctrine's central untested question, never opened.
+- Statusline occupancy unverified before recommending it as the fool's body.
+
+### Authorization moves — 2026-08-22, third batch (v2)
+
+- **v2 stored verbatim** (`ed2861ee…`), supersession header; **v1 retained unaltered** (`9aceed7f…`)
+  as v2 directs. PENDING-149 AMENDMENT 1 filed.
+- **First v2 send was byte-identical to v1** — `diff -u` empty, both bodies `72af4115…`. Reported
+  as a paste error, **not filed as an amendment**. Trusting the label would have put a supersession
+  marker over unchanged text.
+
+### What held — 2026-08-22, third batch
+
+- ✅ **§8a's flagged assumption closed by checking, not assuming.** `statusLine` NOT SET in any of
+  the three settings files ⇒ the surface is free, nothing displaced, body/voice implementable.
+- ⚠ **§6b's provenance commit verified against git and its RATIONALE is false.** `3b0730d5` exists
+  and holds exactly one `CLAUDE.md` (mechanics sound), but it is dated **2026-08-06** — five days
+  AFTER the fool was conceived (trial 01, 08-01) — its subject names the **PENDING-89 docket**, and
+  **Constraint 6 is already in it** (placed `c30dfe0`, 08-02). So "seeded from the constitution as
+  it stood before the fool was conceived" is false: the fool would be seeded from the very doctrine
+  §11 forbids it from being cited as satisfying. The commit matching the rationale is `4d2ae87`
+  (2026-07-28). **Not changed — the hash is the jurist's and steward's, not a [FIX].**
+- **Both findings came from opening the substrate rather than reading the document's own claim
+  about itself** — the same act that failed three times this week, run deliberately this time.
+
+### Open horizons — 2026-08-22, third batch
+
+- ⚠ **TIME-CRITICAL: beacon timestamp 2026-08-25T12:00:00Z, three days out**, and §4 requires the
+  seed rule filed and pushed BEFORE it. §6b disposition + `<DATE FILED>` both needed first.
+- ⚠ **§5 ratification ambiguous** — v2's heading says "ratified by the steward", §13.7 says nothing
+  runs until ratified. Treated as NOT ratified (conservative; undoable only by waiting).
+- **No beacon pulse fetched**, target or near-future. No dry run attempted.
+- Owed under §15b: state the zero-contribution in PENDING-89; open the v1 Chamber archive read as
+  its own [PROPOSAL].