[HARDENING] PENDING-89: write in that the buddy fool contributes zero, by construction

Steward's direction, and the timing is the reason: the fool acquired bones today.
It is now the most visible object in the programme, it has a seed and a rule and a
draw, and PENDING-89 is starving. Those two facts sitting unremarked next to each
other invite exactly the wrong inference, so the zero is stated rather than left
inferable.

Three clauses cited, each READ before citing rather than recalled — and one is
sharper than the recalled version. The bar is not buried in §11; §2 states it
outright: "Not an answer to Constraint 6. See §11." §9 files nothing anywhere, so
there is no record of misses to correlate, ever. §11 says three of four parties
sharing formation makes Constraint 6's concession worse, so seating it SUBTRACTS on
the doctrine's own strong/weak distinction.

Stated symmetrically on purpose: a fool that fires usefully proves nothing here, and
a fool that fires uselessly disproves nothing here. The bar runs in both directions
or it is not a bar.

Names where the evidence actually lives — PENDING-151's v1 Chamber archive (9
formation pairs, already authorized as REVIEWED-125 source (iv), and the only place
two formations have read the same text; bounded to GENERATION diversity and never
correlation of misses, per R-125) and PENDING-153's Thistleweld read.

That sharpens the 2026-08-20 note rather than answering it: no new instrument feeds
this item, still true. But the gap's shape changes — it waits on two already-filed,
already-authorized reads to be PERFORMED, not on anything to be built. Starving for
want of execution is the cheaper condition to end.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf

PENDING.md

@@ -897,6 +897,51 @@ datum, n=1; (ii) the 2026-08-20 FL5 datum immediately above; (iii) the 2025 arm,
 found-not-run. **No new instrument currently feeds this item.** Named by the jurist, 2026-08-20,
 and recorded here at its direction — the gap is created by the re-aim, not discovered later.
 
+### Docket entry 2026-08-25 — the buddy fool contributes ZERO to this item, by construction
+
+*Written in explicitly, at the steward's direction, on the day the fool acquired bones. The point of
+saying it here rather than leaving it inferable: **every day this sits unstated, the fool looks more
+like evidence for a question it cannot address.** It is the most visible object in the programme, it
+now has a seed, a rule and a draw, and this item is starving — the two facts sit next to each other
+and invite exactly the wrong inference.*
+
+**Not a shortfall. A design property, ratified in REVIEWED-125, and checkable in three clauses of
+the v2 doctrine (each read before being cited here, not recalled):**
+
+| clause | what it says | why PENDING-89 gets nothing |
+|---|---|---|
+| **§2** | *"Not a checker, auditor, reviewer, or devil's advocate. **If its output can be graded, the design has failed.**"* — and, in its own words, *"**Not an answer to Constraint 6. See §11.**"* | This item's question is whether a **checking** position is independent. The fool is constitutionally not a checking position, and the doctrine says so directly rather than leaving it to interpretation. |
+| **§9** | *"Output reaches **the steward**. Filed nowhere. No `PENDING` entry, no log, no item."* | Correlation of misses requires a **record of misses**. The fool produces none, deliberately — the unfileability is what keeps it uningestible. There is nothing to correlate, ever. |
+| **§11** | If the fool runs on Claude, **three of four parties share formation** — which makes Constraint 6's concession *worse rather than better*. | Seating it does not add an independent position. On the doctrine's own strong/weak distinction it **subtracts**, and §11 was written to say so at the outset rather than be discovered later. |
+
+⚠ **So the fool must never be cited toward this item, in either direction** — not as evidence that
+the arrangement is checked, and not as evidence that it is not. A fool that fires usefully proves
+nothing here; a fool that fires uselessly disproves nothing here. Any future entry that reaches for
+it has misread §2.
+
+**Where this item's evidence actually lives** — the sources are retrospective, and both of the real
+ones are already filed and already authorized to read:
+
+1. **The v1 Chamber archive — `PENDING-151`, and the strongest source available.** 9 complete
+   formation pairs, 6 sessions, 19,479 words; **AUTHORIZED to read** as REVIEWED-125 source (iv).
+   It is the only place in this system where **two formations have already read the same text**, and
+   it passes the self-authored-corpus test outright: produced in 2025, before the contamination
+   doctrine existed and before any of this reasoning. ⚠ **Bounded, and REVIEWED-125 binds it:** it
+   answers **generation** diversity — two voices producing a reading — and **never correlation of
+   misses**, which is readers auditing a proposal. Different objects. It may not be reported as the
+   latter under any framing.
+2. **The Thistleweld corpus — `PENDING-153`,** the kind-3 read: the arrangement critiqued from
+   outside it. Closest thing on hand to an outside position, and it exists.
+3. The three retrospective datums already listed above: trial-04 (n=1), the 2026-08-20 FL5 datum,
+   and the 2025 arm recorded as found-not-run.
+
+**Which sharpens the note above it rather than answering it.** That note says no new *instrument*
+feeds this item after the re-aim. That remains true and is unchanged by anything here. What changes
+is the shape of the gap: this item is not waiting on something to be built — **it is waiting on two
+already-filed, already-authorized reads to be performed.** Starving for want of execution is a
+different condition from starving for want of an instrument, and it is the cheaper one to end.
+
+
 ## PENDING-90 — First L2 transfer: checker position in the calibration loop
 **Date:** 2026-08-02
 **Tag:** [ESCALATE]
@@ -4930,3 +4975,33 @@ and obeyed, which is the described-not-invoked class that had the link canary ha
 a first firing is observed on the live path* — since (b) is now run and (a) would re-derive it.
 
 **Awaiting:** Steward authorization.
+
+---
+
+## PENDING-157 — The deferral schema has no resolution state, so every discharge is a hand-rename
+**Date:** 2026-08-25
+**Tag:** [HARDENING]
+**Summary:** `DEFERRED-DECISION` declares `since` / `owner` / `trigger` / `discriminator` and nothing for *answered*, so a decision that has been taken can only be closed by deleting the block (losing the record) or renaming its key by hand (losing machine-checkability, and depending on the reflex the mechanism exists to replace).
+
+**Rationale.** Today `fool-beacon-derivation-run-once` fired for real, the act ran, and the block was closed by renaming it to `DISCHARGED-DECISION`. That worked, and it is per-instance. The next trigger to come due will need the identical manual rename, performed correctly, by whoever happens to be in session.
+
+This is the shape census 01 already found: **decay, not construction, is how gates fail here.** A schema that cannot express "answered" *produces* the decay — the only alternatives it offers are erasing the record or a reflex, and a reflex is precisely what a trigger mechanism is built to stop relying on. Renaming keys one at a time is how one lives with the defect rather than fixing it.
+
+⚠ **Filed now, deliberately, while there is exactly one instance.** Three tracked deferrals remain checkable; the moment a second one comes due and is renamed by habit, the convention is established and the schema question stops being asked. That is the window this item exists to beat, and the reason it is filed rather than deferred.
+
+**The sharper half — a status field alone is not enough.** The genuine failure available here is a discharge that records *that* a gate closed but not *what* closed it: six months on, a reader learns a decision was answered and cannot find the answer. So resolution should be **unsatisfiable without a pointer** — the schema should make an undocumented discharge impossible to express, not merely discouraged.
+
+**Options.**
+1. **`resolved: YYYY-MM-DD — <pointer>` field, required to be non-empty, parser skips resolved blocks for due-ness but still parses and validates them.** The key stays `DEFERRED-DECISION`; nothing is renamed; the block remains machine-readable forever.
+2. `status: open | resolved | superseded`, same pointer requirement. More expressive, more surface.
+3. Keep the rename convention and document it. Cheapest; leaves the reflex in place, which is the thing being complained about.
+
+**Recommendation: (1), with two conditions.**
+- **The parser must keep counting resolved blocks and report them as a closed ledger**, not drop them silently. A discharge that vanishes from the report is its own species of decay — the register would show three tracked deferrals and no evidence a fourth was ever answered.
+- **A resolved block whose pointer is missing or unresolvable must be reported as a defect**, in the same register-integrity lane that already catches an amendment which replaced the record it amends. Same failure family: a record that closes over its own history.
+
+**Verification required before it is trusted** (per the standing rule that an absence is not evidence until the instrument is shown able to detect presence): a positive control that a resolved block with a past-date trigger is **not** reported due; a negative control that an *unresolved* block with the same past date **is**; and a third that a resolved block with an empty or dangling pointer is flagged.
+
+**Files affected:** `scripts/governance-drift-check.py` (parser, due-ness, register-integrity lane, selftest); `PENDING.md` — the one existing `DISCHARGED-DECISION` block reverts to `DEFERRED-DECISION` with `resolved:` set, which is also the migration's own test case.
+
+**Awaiting:** Steward authorization. **Not urgent, and not open-ended:** the condition that makes it urgent is a second trigger coming due, and there are three that can.

claude/governance/fool/BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md

@@ -108,7 +108,7 @@ Each step committed and pushed before the next begins.
 
 1. Perception axes ratified by the steward (§5).
 2. Seed derivation rule filed, naming a **future** timestamp (§6).
-3. Abandonment criterion filed (§10).
+3. Retirement criterion filed (§10).
 4. Regeneration criterion filed (§10).
 5. Timestamp passes; seed computed; bones derived.
 6. Soul generated once from the bones (§7).
@@ -116,6 +116,22 @@ Each step committed and pushed before the next begins.
 Steps 1–4 complete and pushed **before** step 5. Axes chosen after the seed is
 known, or with a fool in hand, smuggle the selection one level up.
 
+⚠ **`[FIX]` 2026-08-25 — step 3 read *"Abandonment criterion"* until today.** §10 has
+always defined **RETIREMENT**; the jurist ruled the fool's own doctrine should carry one
+word with one meaning (recorded in `seed/FOOL-SEED-RULE.md` §5b), and scheduled the
+harmonization **after** the beacon so no edit touched the filed rule before it fired. It
+fired 2026-08-25T12:00:00Z; this is that harmonization. **The criterion itself is
+unchanged — only the word naming it.**
+
+*Abandonment* is deliberately left standing where **§6 of the trial-09 design** owns it:
+a different criterion, about the jester form, assessed across trial 09 and one frontier
+replication. Thirteen occurrences there were censused and left untouched.
+
+⚠ **The prior wording is recorded here rather than silently replaced.** REVIEWED-125
+ruled on this document's text. An edit that leaves no trace makes the ruling's subject
+drift from the artifact it ruled on — the hazard PENDING-82 / PENDING-86 already track,
+and which this very item's record notes recurring *inside* a ruling.
+
 ## 5 · Perception axes — five, ratified by the steward
 
 Five axes, 0–100. Each is something the fool could be **blind to**. The steward
@@ -402,8 +418,9 @@ negligible cost. Do not build for it now; do not preclude it.
 1. Spec document in the governance tree, provenance header naming this v2 draft
    and what was changed.
 2. Status-line availability confirmed (§8a) **before** §8 is implemented.
-3. Filed axes, seed rule (both components, §6), abandonment and regeneration
+3. Filed axes, seed rule (both components, §6), retirement and regeneration
    criteria — committed and pushed **before** the beacon timestamp.
+   *(`[FIX]` 2026-08-25: read "abandonment" until today — see the note under §4.)*
 4. Derivation implementation: deterministic, fresh-overrides-stored, no reroll
    path, **no salt from any reference implementation.**
 5. Post-derivation record per §6a, in a single commit: raw beacon value, seed

claude/governance/fool/seed/FOOL-BONES-2026-08-25.md

@@ -103,7 +103,32 @@ updated. **Internal to the rule, affects no value in this record**, and §5b bin
 edit touches the rule before it fires. Owed as a `[FIX]` alongside the
 `abandonment` → `retirement` harmonization.
 
-## 6 · What has NOT happened
+## 6 · The trigger that fired this
+
+This derivation had **no trigger of any kind** until 2026-08-24 — no cron, no launchd, no
+scheduled agent, and not a tracked deferral. An authorized, dated, irreversible, run-once
+act resting entirely on someone remembering. A `DEFERRED-DECISION` block was added that
+day and proven by positive control (with the date temporarily set to the past, the checker
+announced it by name).
+
+**It fired for real at the 2026-08-25 wake**, naming `fool-beacon-derivation-run-once`
+under COME DUE — the first time the mechanism carried a live firing rather than a
+rehearsal. That is what put this derivation in front of the executor.
+
+It is now **discharged**, in `~/dotfiles/PENDING.md`, by renaming the key to
+`DISCHARGED-DECISION` — `governance-drift-check.py`'s parser has no `resolved:` field, so
+a taken decision would report COME DUE forever. Commit `06b3d8b`. Verified after: the
+checker went from *"1 of 4 have COME DUE"* to *"3 tracked, none due"*.
+
+⚠ **The per-instance rename is not a fix.** A schema with no resolution state is what
+produces the decay; renaming keys one at a time is how one lives with it. Filed as
+**PENDING-157 `[HARDENING]`** against the schema itself, deliberately before a second
+trigger comes due and gets renamed by reflex.
+
+*(Written at both ends: the discharge block points here, and this points back. Pointing
+one way only is how a successor learns that a gate was closed but never why.)*
+
+## 7 · What has NOT happened
 
 - No soul generated. §8 (proportions — still *"low, fixed"* with no number), §8a (body
   design) and §9 remain unbuilt.

claude/governance/fool/seed/FOOL-SEED-RULE.md

@@ -182,14 +182,18 @@ precisely because it would soften the dump.
 
 ## 4 · Pre-registered criteria (§4 steps 3 and 4)
 
-⚠ **Naming note:** §4 step 3 calls for an *"abandonment criterion"*; §10 defines
-**RETIREMENT**. They are the same criterion under two names; §10 is the referent.
+⚠ **Naming note — RESOLVED 2026-08-25.** §4 step 3 of the doctrine called for an
+*"abandonment criterion"* while §10 defined **RETIREMENT**: the same criterion under two
+names, with §10 as the referent. The jurist ruled one word with one meaning, and the
+harmonization ran after the beacon (§5b, §7). The doctrine now reads *retirement*
+throughout; *abandonment* stands only where **§6 of the trial-09 design** owns it, in its
+own sense about the jester form.
 
 **REGENERATION** — permitted ONLY on a demonstrable implementation error, verified
 against this filed rule. **Not because the output is disliked.** A re-run against the
 same recorded `outputValue` is legitimate; a re-run against a later pulse is a new draw.
 
-**RETIREMENT (abandonment)** — only on mechanical failure: does not fire; fires
+**RETIREMENT** — only on mechanical failure: does not fire; fires
 constantly; or produces gradeable in-genre findings despite §9.
 
 **NOT grounds for retirement:** being uncomfortable, being frequently wrong, being
@@ -261,21 +265,58 @@ normalization point, and it is in the code.
 
 ## 5b · Owed after the 25th, non-blocking
 
-**`[FIX]` — 'abandonment' → 'retirement' throughout the fool's doctrine.** The jurist
-owns the mismatch (§4 step 3 says *abandonment*, §10 defines *RETIREMENT*) and rules that
-the fool's own doctrine should read **retirement**, one word with one meaning —
-*abandonment* is the word §6 of the trial design owns, with a specific sense about the
-jester form. Naming rather than silently harmonizing was correct; the harmonization is a
-`[FIX]` **after** the beacon, so no edit touches this rule before it fires.
+✅ **`[FIX]` — 'abandonment' → 'retirement' throughout the fool's doctrine. DONE
+2026-08-25**, after the beacon fired, as this clause required. The jurist owned the
+mismatch (§4 step 3 said *abandonment*, §10 defines *RETIREMENT*) and ruled that the
+fool's own doctrine should read **retirement**, one word with one meaning — *abandonment*
+is the word §6 of the trial design owns, with a specific sense about the jester form.
+Naming rather than silently harmonizing was correct.
+
+**Executed as a censused edit, not a blanket replace.** All 24 `abandon*` occurrences in
+the fool tree were counted and read in context first: **9 were doctrine and changed**
+(2 in the v2 draft, 5 here, plus this clause); **13 in the trial-09 family were left
+untouched**, being §6's own criterion; **1 in `input-dependence-01`** is ordinary English
+about the void of a numbering; **1 in `FOOL-BONES-2026-08-25.md`** is the dated record of
+what was owed. Prior wording is preserved in place at every changed site rather than
+overwritten — REVIEWED-125 ruled on the v2 draft's text, and an untraceable edit drifts a
+ruling's subject from its artifact.
 
 **The mumble-hook answer** (v2 §8) — clock-governed, event-checked, residual burst
 sensitivity declared rather than claimed away. The daemon alternative to be **costed, not
 dismissed**. A build decision, not a governance one. Also after the 25th.
 
-## 6 · What has NOT happened
+## 6 · What had NOT happened — as of filing, 2026-08-22
 
-- The target pulse has **not** been fetched. No near-future pulse has been fetched.
-- No bones have been derived. No soul has been generated.
+⚠ **SUPERSEDED IN PART, 2026-08-25.** The first two bullets became false the moment the
+derivation ran, and a governance document asserting stale current state is the failure
+Constraint 4 forbids. They are preserved verbatim-struck rather than deleted, because
+they are the **pre-registration record** — what this document claimed *before* the beacon,
+which is the entire point of having filed it early. Current state lives in
+`FOOL-BONES-2026-08-25.md`.
+
+- ~~The target pulse has **not** been fetched. No near-future pulse has been fetched.~~
+  → **Fetched 2026-08-25 ≈12:38Z**: pulse `2026-08-25T12:00:00.000Z`, chain 2, index 1917365.
+- ~~No bones have been derived. No soul has been generated.~~
+  → **Bones derived 2026-08-25**, once, commit `5694b925`. **No soul generated** — that
+  remains true, and §7 of the doctrine is unrun.
 - `~/CLAUDE.md` has **not** been touched (PENDING-150, unbundled).
 - Nothing has been implemented of §8, §8a or §9 — the status line is confirmed free but
   not built.
+
+---
+
+## 7 · Post-beacon edits to this rule — the audit trail
+
+This document's worth rests on having been **filed and pushed before the beacon
+timestamp**. Every edit made after 2026-08-25T12:00:00Z is listed here, so that property
+stays auditable instead of eroding one silent correction at a time.
+
+| date | what changed | authority | did it govern the derivation? |
+|---|---|---|---|
+| 2026-08-25 | `abandonment` → `retirement`: §4's alias and naming note, §5b marked done | jurist ruling recorded in §5b, which itself scheduled the change *after* the beacon | **no** — the word naming a criterion, never the criterion |
+| 2026-08-25 | §6 marked superseded in part | Constraint 4, honest degradation | **no** — §6 is a status claim, not a rule |
+
+⚠ **Nothing in §1, §2, §2a, §3, §5 or §5a has been edited.** Those are the clauses that
+governed the derivation, and they stand exactly as they stood when it ran. This is not an
+assertion of good intent: it is checkable, and was checked — `git diff` was read hunk by
+hunk against the pre-edit commit to confirm no hunk falls inside them.