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
