session 2026-08-25: the beacon fired, Tarbuckle named and voiced, STATE-CLAIM built

Session state, memory index, KG and the Symmetria ledger. Carries the steward's own
placement of REVIEWED-127 off-disk — preservation, not modification: it was found
staged during the wrap by §6.5's own guard, which is exactly the case that clause
exists to catch, and the answer was benign.

Verified rather than assumed at placement: the placed ruling is byte-identical to the
executor's draft, 3,523 bytes both sides. No drift between a ruling's subject and its
artifact — the PENDING-82/86 class, checked because it is cheap and because this record
already notes that class recurring inside a ruling.

The draft file is SUPERSEDED IN PLACE rather than deleted: it is now a parallel version
of a canonical record, and an unmarked parallel version is the context-rot failure. It
points at REVIEWED.md and says not to edit it. Both PENDING items updated from "drafted
for steward placement" to placed — a line that went false the moment the steward acted.

MEMORY.md 22,368 bytes, prior Active Session demoted verbatim into MEMORY-reference.md
on promote. Fool tracker rewritten: it named a superseded workstream (trial 09,
re-aim) and now names Tarbuckle, the sealed artifacts, and the honest state that
NOTHING IS WIRED. N-now 51.

KG +6: three drift-patterns (vigilance did not prevent the failure it was vigilant
about; filed a non-defect as a defect twice in one direction; a control fixture pointing
at a file the session was editing) and two preventions (recusal preserved the only party
able to answer; censusing 24 occurrences stopped a blanket replace from destroying the
distinction the fix existed to create).

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

REVIEWED.md

@@ -2213,4 +2213,48 @@ systematically under-record the second.
 **If AUTHORIZED:** build `~/dotfiles/scripts/daybook-mcp.py` with conditions 1 and 3
 satisfied and a selftest carrying paired positive/negative controls. Do NOT install:
 installation awaits condition 2 being named and met. `claude_desktop_config.json` merge
-and app restart remain the steward's hand.
+and app restart remain the steward's hand.
+
+## REVIEWED-127 — PENDING-157 + PENDING-158 — The deferral schema's missing halves, ruled jointly
+**Date:** 2026-08-25
+**Decision:** AUTHORIZED — both, jointly
+**Notes:**
+- **The generalization argument carries the ruling.** `DEFERRED-DECISION` exists because deferrals
+were being forgotten; its own comment says a deferral is the claim *not yet*, and the trigger fires
+when the substrate contradicts it. **A negative state-claim is that sentence about a different
+object** — *not yet* about a state rather than a decision. Same words, same forgetting, same
+substrate standing ready. One got a machine-checkable trigger weeks ago. The other got nothing, and
+nobody noticed they were the same shape. That is a real finding, and it is what is authorized.
+- **Ruled together deliberately.** Half a schema invites a third patch, and a third patch is how a
+vocabulary accretes instead of being designed. 157 gives deferrals a resolution state; 158 gives
+states a falsifier. Neither ships alone.
+- **What carries the ruling and what does not.** The 3-of-5-on-existing-vocabulary and
+5-of-5-with-two-new-kinds figures were **run**, not asserted, and that is what makes this a
+generalization rather than a proposal. The **57 is a grep** and is correctly not called a census;
+that line is held as a standing condition in the item because **57 will get quoted**.
+- **On the diagnosis change — recorded in the ruling, not left in the item.** The first reading was
+*negative-status lists are fragile*, a property calling for care. The evidence against it is
+decisive: **the third instance occurred inside the section naming the pattern, hours after it was
+written, by an executor explicitly watching for it.** Maximum attention, immediate recency, explicit
+vigilance — and it still happened. That is as close to a controlled demonstration as this record
+will produce. **Care is not a mechanism.** Stated here because *be careful* is what a later reader
+will otherwise reach for.
+- **Condition C1 — `STATE-CLAIM` inherits 157's resolution state; it does not ship with a trigger
+alone.** The 25th already exposed the gap: a trigger came due, was correctly discharged by renaming
+the key, and would otherwise have reported COME DUE forever. If `STATE-CLAIM` ships with the same
+shape, discharge is again a manual rename and the decay returns one layer along. If 157 does not
+address `resolved:`, that is a third patch already visible from here.
+- **Condition C2 — opt-in is accepted, and its limit is stated in the item rather than discovered.**
+An opt-in marker catches claims by authors who remember to mark them, which is the same population
+that would have caught them anyway. The 57 are unmarked. **Adoption is the open question, not
+expressibility.**
+- **The motivating evidence was recovered by luck, and the item says so first.** The five-day pair
+surfaced because a false belief was stated aloud and found false; the pair had already survived five
+days, a jurist ruling, and several sessions in that directory. An accident with no reproduction path
+is the clearest statement of what currently exists: nothing. Placed at the head of PENDING-158 at
+this ruling's direction.
+
+**If AUTHORIZED:** Proceed. Build both together, 157 first or in the same change, with the controls
+the items name: a state-claim whose falsifier has fired IS reported; one whose falsifier has not
+fired is NOT; `manual` is listed but never fired; a resolved block with a missing or dangling
+pointer is a register-integrity defect. Tag commits REVIEWED-127.