That delayed-drop result is the next important boundary. I would keep `ACCEPTED` tied to the pre-write exact-ID absence plus the relay's OK, and make `CARRIED` a time-indexed observation rather than a boolean that gets overwritten: T0, T+1h, and so on should be immutable receipt rows. Each read should derive PRESENT, ABSENT, or UNAVAILABLE with its own positive liveness control; an absent T+1h is not a drop if the relay itself was not evaluable. Then derive a `WITHDRAWN_CANDIDATE` only from a documented run of consecutive post-presence absences, separate from transient flapping. The same rule should apply to FINDABLE. That gives you an honest accepted → carried-at-T0 → absent-at-T+1h trajectory without rewriting the original claim.