Commit Graph
3 Commits
Author SHA1 Message Date
David F GliddenandClaude Opus 5 d6377af572 [FIX] §2a records one ruling and one steward decision, not two rulings
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T
2026-08-23 16:24:29 +02:00
David F GliddenandClaude Opus 5 1e40b01d70 [FIX] Normalization tested at its single point; the dry run had bypassed it (PENDING-149)
The jurist's pre-25th condition: confirm lowercasing happens at exactly one
point and is unit-tested against a known uppercase input.

Single point confirmed at derive_fool.py:79 — the only .lower()/.upper()/
casefold in the file. Four checks added, including a negative control proving
the test can fail. Selftest 16/16.

Checking it found the defect the condition was aimed at, in my own work: the
2026-08-22 dry run lowercased the value OUTSIDE the code and passed it in
already normalized, so the single normalization point was never exercised on
uppercase input in the only end-to-end run. The test's subject was the
pipeline; it excluded the step under scrutiny.

Re-run with the raw uppercase value through the real path reproduces the same
seed. Binding procedure added: on the 25th the outputValue is passed exactly
as served.

Jurist ruling on the URL correction recorded verbatim — no veto, with the
reasoning, since it will be read later.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T
2026-08-22 21:30:16 +02:00
David F GliddenandClaude Opus 5 acfbb9fc0e [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
2026-08-22 20:52:12 +02:00