The first announcement commits generation zero before requesting expiry.
Greater evidence versions refresh with a checked fresh generation; identical
evidence is idempotent and does not reschedule. Lower or contradictory
evidence is rejected atomically. A timer-key collision with another live
participant is rejection, never replacement. Matching elapsed evidence
commits an explicit tombstone and reports expiry. Generations advance per
timer key across every retained participant tombstone, so reuse by a later
participant cannot reinterpret delayed evidence from an earlier owner;
stale and unknown timer evidence is inert. Initialization is empty, no actors are created, and the
host never terminates by policy. Versioning, first-observation ordering,
timer mapping, and tombstone retention are Bombay policy. Scheduling belongs
to Timers; release/cancellation is not part of this announcement protocol.
No transition has a semantic panic condition.
Consume this definition, perform its one initialization fold, and
return the active behavior together with the ordered initialization
effects. Read more