[HARDENING] File PENDING-157: the deferral schema has no resolution state

The steward's scope point on yesterday's discharge, taken. Renaming the key closed
one trigger; the next will need the same hand-rename by whoever is in session. If
census 01 found decay is how gates fail here, a schema that cannot express "answered"
is what produces the decay, and renaming keys one at a time is living with it.

Filed while there is exactly ONE instance and three tracked deferrals remain. The
window matters: once a second is renamed by habit the convention is established and
the schema question stops being asked. Filed, not built — that was the direction.

Carries a sharper half the rename surfaced: resolution must be unsatisfiable without
a pointer, so a discharge that records THAT a gate closed but not WHAT closed it
becomes impossible to express rather than merely discouraged. Plus two conditions on
the recommendation (resolved blocks stay counted as a closed ledger; a dangling
pointer is a register-integrity defect) and three required controls.

Also writes the missing reverse pointer into FOOL-BONES §6. The discharge block
already pointed at the derivation record and 06b3d8b's message named it; the record
did not point back. Written at both ends now — one direction only is how a successor
learns a gate was closed but never why.

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

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.