From d6377af572bed38750c00033a8c173d3bdf04e7d Mon Sep 17 00:00:00 2001 From: David F Glidden Date: Sun, 23 Aug 2026 16:24:29 +0200 Subject: [PATCH] =?UTF-8?q?[FIX]=20=C2=A72a=20records=20one=20ruling=20and?= =?UTF-8?q?=20one=20steward=20decision,=20not=20two=20rulings?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The heading read "Two corrections to the v2 §6b block — RULED, no veto" while the ruling beneath it addressed only the retrieval URL. Its settling test — "could this correction have moved the outcome?" — returns no for the URL and YES for the provenance commit, since the provenance SHA is half the seed string. The heading therefore claimed a scope the ruling could not reach. Jurist confirmed 2026-08-23: "I ruled on one thing. The URL." The provenance commit was never a correction under veto — the steward selected a still-open value on the jurist's recommendation, before filing. It is now recorded as a steward decision of 2026-08-22, with its reasoning, because a value that moves the outcome must be attributable to the party entitled to choose it. Verified independently against git, not relayed: 4d2ae87 = 2026-07-28 11:32:39 +0200; trial 01 = 2026-08-01 (four days later) last commit to CLAUDE.md before trial 01 (next is c30dfe0, 2026-08-02) "Differently biased checkers": 0 at 4d2ae87, 1 at 3b0730d5 blob SHA re-derived = 2d6e250a...120d, matches the filed value EDIT IS INERT WITH RESPECT TO THE DRAW, proven rather than asserted. The filed discipline is that no edit touches this rule before it fires; derive_fool.py does not read this document — it hardcodes its constants and recomputes the provenance SHA from git — so prose cannot steer the draw. Same synthetic vector before and after gives the identical seed 3d8cc243f9b6ffc5fc7d254306ca4ca135a71d76d483df924736a18345fb8b7a; selftest passes; diff removes no constant line. rule sha256 before: e1fa6fb3e4f928e468dc102f011d554c20eb14d9b49c17ce1f6f839106179bff rule sha256 after: fb11818dd2e3c2bdcf21e2740fc3110a7aa9a9ead57098a93f27b9051d438551 The synthetic vector above is not a pulse and its output is not bones. Refs PENDING-150 AMENDMENT 2/3, REVIEWED-125 AMENDMENT 1. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T --- claude/governance/fool/seed/FOOL-SEED-RULE.md | 54 ++++++++++++++----- 1 file changed, 40 insertions(+), 14 deletions(-) diff --git a/claude/governance/fool/seed/FOOL-SEED-RULE.md b/claude/governance/fool/seed/FOOL-SEED-RULE.md index 9b5239e..374c631 100644 --- a/claude/governance/fool/seed/FOOL-SEED-RULE.md +++ b/claude/governance/fool/seed/FOOL-SEED-RULE.md @@ -89,10 +89,11 @@ TESTING a near-future pulse. ``` -### 2a · ⚠ Two corrections to the v2 §6b block — RULED, no veto +### 2a · ⚠ One correction RULED (the URL) · one STEWARD DECISION (the provenance commit) -⚠ **JURIST RULING, 2026-08-22: no veto; the correction stands.** Recorded with its -reasons, since it will be read later. +⚠ **JURIST RULING, 2026-08-22 — scope: the retrieval URL, correction (b) below, and +nothing else. No veto; the correction stands.** Recorded with its reasons, since it will +be read later. > The UNAVAILABILITY clause forbids substituting a different **timestamp, beacon, or > source**. None of the three changed. Same beacon (NIST v2.0), same pulse @@ -107,20 +108,45 @@ reasons, since it will be read later. > would have guaranteed a stop on the 25th for a reason unrelated to entropy — the > opposite of what it protects. -**The two corrections, marked rather than silent:** +⚠ **The ruling above does not reach (a), and was never offered as reaching it.** +Confirmed by the jurist, 2026-08-23: *"I ruled on one thing. The URL."* Its settling test +— *could this correction have moved the outcome?* — returns **no** for the URL and **yes** +for the provenance commit, since the provenance SHA is half the seed string. A value that +moves the outcome is attributable to the party entitled to choose it. **This heading +previously read *"Two corrections … RULED, no veto"* and over-claimed the ruling's scope.** + +**One correction and one decision, both marked rather than silent:** The draft said to commit its block verbatim. **Two values in it do not resolve**, and a -rule that cannot be resolved on the day is not a rule (v2's own standard). Both changes -are recorded here for veto rather than absorbed quietly. +rule that cannot be resolved on the day is not a rule (v2's own standard). -**(a) The provenance commit — changed on the steward's direction, 2026-08-22.** -`3b0730d59336113aa3a500a889a3e154be6a1de7` → `4d2ae87a4e5350c4d3bb3aa50f9544b521d9c53d`. -The draft's stated rationale — *"the constitution as it stood before the fool was -conceived"* — was false of the original: it is dated 2026-08-06, five days after trial -01, its subject line names the **PENDING-89 docket** (the question §11 forbids the fool -from being cited on), and **Constraint 6 is already present in it**. Verified: at -`4d2ae87` (2026-07-28) `Differently biased checkers` occurs **0 times**, and exactly one -`CLAUDE.md` exists at that commit. +**(a) The provenance commit — a STEWARD DECISION of 2026-08-22, taken on the jurist's +recommendation. Not a correction, and not under veto.** +`3b0730d59336113aa3a500a889a3e154be6a1de7` → `4d2ae87a4e5350c4d3bb3aa50f9544b521d9c53d` + +**The sequence, as the jurist records it (2026-08-23):** the steward proposed +`3b0730d5`; the jurist wrote a rationale for it; the executor found the rationale **false +of that commit** and offered three dispositions; the jurist recommended (ii), switching to +`4d2ae87`; **the steward chose it, while the value was still open and before anything was +filed.** There was nothing to veto — this is the steward selecting a value entitled to him, +not the executor amending a filed rule. + +**Why the original rationale failed.** *"The constitution as it stood before the fool was +conceived"* is false of `3b0730d5`: it is dated **2026-08-06**, five days after trial 01, +its subject line names the **PENDING-89 docket** (the question §11 forbids the fool from +being cited on), and **Constraint 6 is already present in it**. + +**Verified against git 2026-08-23 — all four re-run independently, not relayed:** + +| check | result | +|---|---| +| `4d2ae87` date | **2026-07-28 11:32:39 +0200** — four days before trial 01 | +| trial 01 date (trials table) | **2026-08-01** | +| last commit to `CLAUDE.md` before trial 01 | ✅ yes — the next is `c30dfe0`, 2026-08-02 | +| `Differently biased checkers` at `4d2ae87` | **0 occurrences** (at `3b0730d5`: **1**) | +| provenance blob SHA re-derived | `2d6e250a…120d` — **matches the filed value** | + +Exactly one `CLAUDE.md` exists at that commit. **(b) The retrieval URL — corrected on evidence, and this is the executor's change.** The block's `GET /pulse?timeGE=2026-08-25T12:00:00Z` **returns HTTP 302 with an empty