Acquisition is accepted only while vacant and commits a fresh generation
before emitting its schedule. Renewal and release require the exact holder
and generation. Matching elapsed evidence expires ownership; wrong timer IDs
and stale generations are inert. Release cannot retract an already queued
elapsed observation, so later evidence is explicitly stale. Once the finite
generation domain is consumed, the vacant state becomes Exhausted and no
successful ownership can be created. Initialization is empty, no actors are
created, and the host never terminates by policy. Exclusivity, checked
generation progression, and commit-before-schedule ordering are Bombay
policy. Scheduling and sleeping belong to Timers. The current Bombay timer
adapter has no cancellation effect lane; release is semantically immediate
while the stale queue entry may remain until due. No transition panics.
Consume this definition, perform its one initialization fold, and
return the active behavior together with the ordered initialization
effects. Read more