---
name: FOOL-BONES-2026-08-25
description: "The derivation record required by FOOL-SEED-RULE.md EXECUTION: raw beacon value, seed string, SHA-256, resulting stats, and the commit hash of the filed rule. The derivation ran ONCE, on 2026-08-25, against the pulse the rule names. This file is the record, not the rule."
metadata:
  node_type: governance-artifact
  type: reference
---

# FOOL BONES — derived 2026-08-25

**Ran ONCE.** No retry, no reroll, no second pulse. Executed by the executor under the
standing authorization filed in `~/PENDING.md` (*"⚠ THE DERIVATION IS AUTHORIZED TO RUN
ONCE — 2026-08-25T12:00:00Z"*, `Awaiting: nothing`).

Governed by **`FOOL-SEED-RULE.md` at commit `d6377af572bed38750c00033a8c173d3bdf04e7d`**
(2026-08-23 16:24:29 +0200) — filed and pushed before the beacon timestamp, and clean in
the working tree at the moment of execution.

## 1 · The pulse

| field | value |
|---|---|
| retrieval | `GET https://beacon.nist.gov/beacon/2.0/pulse/time/1787659200000` via **curl**, HTTP 200, 3633 bytes |
| `uri` | `https://beacon.nist.gov/beacon/2.0/chain/2/pulse/1917365` |
| `timeStamp` | **2026-08-25T12:00:00.000Z** — the pulse the rule names, exactly |
| `chainIndex` / `pulseIndex` | 2 / 1917365 |
| `cipherSuite` / `period` | 0 / 60000 |
| fetched at | 2026-08-25 ≈12:38Z (≈38 min after the pulse; the rule reads *"at or after"*) |

Raw response preserved verbatim alongside this file: `beacon-pulse-2026-08-25T120000Z.json`.

**`outputValue`, EXACTLY AS SERVED — recorded before anything was run:**

```
A50999DF9BCDA48CC5898B21FD34630003BF96921EF581F258FCF5DAFE05001155F0290148BCF8F5D8F634B2CFBF2D7EB2C93175612298FE5BF2343C67E9F20C
```

128 hex characters, **UPPERCASE** — as the 2026-08-22 historical dry run predicted, which
is why §5's *"lowercased before use"* is load-bearing rather than cosmetic.

**Passed to `derive_fool.py --beacon` exactly as served**, via `argv`, with no `.strip()`,
no `.lower()`, no hand edit and no shell case transformation anywhere before the call. The
single normalization point at `derive_fool.py:79` did the lowering, and the passed string
was asserted byte-equal to the JSON field before the subprocess ran.

## 2 · The seed

| component | value |
|---|---|
| provenance SHA-256 | `2d6e250a347d25698fb147f80e2dababbb930c4b3b3f9bb822478f360153120d` |
| beacon `outputValue`, normalized | `a50999df9bcda48cc5898b21fd34630003bf96921ef581f258fcf5dafe05001155f0290148bcf8f5d8f634b2cfbf2d7eb2c93175612298fe5bf2343c67e9f20c` |

**`seed_string` = `<provenance>` ‖ `<beacon-lowercased>`:**

```
2d6e250a347d25698fb147f80e2dababbb930c4b3b3f9bb822478f360153120da50999df9bcda48cc5898b21fd34630003bf96921ef581f258fcf5dafe05001155f0290148bcf8f5d8f634b2cfbf2d7eb2c93175612298fe5bf2343c67e9f20c
```

**`seed` = SHA-256(seed_string):**

```
6ea9383bb0b1b3023b1b5507c4ea820b8e07714dd76ff2ca32a1abfc885af05d
```

## 3 · The bones

| axis | stat | |
|---|---|---|
| **SUCCESSION** | **96** | ← **peak** |
| **ABSENCE** | **8** | ← **dump** |
| AIM | 75 | scattered |
| SCALE | 60 | scattered |
| STAKE | 29 | scattered |

Peak in `85–100`, dump in `0–15`, three scattered in `25–75` — the ranges filed in §3 on
2026-08-22, before the beacon value existed. The permutation over the ratified axis order
was driven entirely by the entropy component.

⚠ **This draw is entropy, not judgement, and must never be read backwards as one.** The
ranges were filed before the value was knowable; the axis assignment came from the NIST
pulse. That a fool sharpest on SUCCESSION and near-blind on ABSENCE is a legible outcome
for this system is an observation about the reader, not evidence about the draw.

## 4 · Verification performed at execution time

Every check below was **run now**, not relayed from the 2026-08-22 record.

| check | result |
|---|---|
| `derive_fool.py --selftest` (no network, synthetic vectors) | **16/16 PASS**, incl. the negative control and both positive controls |
| provenance blob SHA re-derived from git, independently of the constant | `2d6e250a…120d` — **matches the filed rule** |
| `seed` recomputed from `seed_string` independently, not read back from `derive()` | `6ea9383b…f05d` — **matches** |
| passed value asserted byte-equal to the served JSON field, and `.isupper()` | **PASS** — as-served uppercase reached `derive()` |
| pulse `timeStamp` equals the rule's named instant | **2026-08-25T12:00:00.000Z**, exact |
| epoch-ms `1787659200000` → instant, verified independently of the rule | **2026-08-25T12:00:00+00:00** |
| `FOOL-SEED-RULE.md` and `derive_fool.py` clean in the working tree at execution | **PASS** — no uncommitted edit governed this run |

## 5 · One discrepancy, named and NOT corrected here

§5 of the filed rule states *"`--selftest` runs 12 checks"*. It now runs **16**: §5a added
four normalization checks on 2026-08-23 and documents them, but §5's count was not
updated. **Internal to the rule, affects no value in this record**, and §5b binds that no
edit touches the rule before it fires. Owed as a `[FIX]` alongside the
`abandonment` → `retirement` harmonization.

## 6 · What has NOT happened

- No soul generated. §8 (proportions — still *"low, fixed"* with no number), §8a (body
  design) and §9 remain unbuilt.
- No retry, no second pulse, no regeneration. §4 REGENERATION is untouched and remains
  available only on a demonstrable implementation error verified against the filed rule.
- `~/CLAUDE.md` not touched (PENDING-150 remains unbundled).
- The filed rule not edited.