Delegate owner boundary and service-state vocabulary.
This module is intentionally small: it does not start a daemon or keep a second durable
store. It names the live-capability boundary required by ADR 0034 so status,
attach, and cancel can report the difference between durable Log snapshots and
active owner-backed behavior.
Current service state:
snapshot_onlymeans durable Log evidence was readable, but no resident Delegate owner is reachable for streaming attach or active cancellation.live_manager_handlesmeans the current BEAM runtime has Subagent Manager handles for active children, but this is not yet a resident Delegate owner.live_delegate_ownermeans this BEAM runtime has a registered Delegate owner for active status/cancel capability. It does not imply cross-invocation daemon residency for one-shot escript callers.stale_handlemeans durable evidence claims work was active, but no live handle exists in this runtime.owner_unavailablemeans the runtime needed for a live operation could not be reached at all.
Summary
Functions
Classify cancel reachability from durable and live Manager evidence.
Return live owner state for a current-runtime Delegate owner.
Build a structured owner-unavailable error for active operations.
Return owner state for a durable snapshot operation.
Build a structured stale-handle error for active operations.
Functions
@spec cancel_state(map(), [map()], [map()], [map()], [map()], keyword()) :: {:ok, map()} | {:error, map()}
Classify cancel reachability from durable and live Manager evidence.
Return live owner state for a current-runtime Delegate owner.
Return owner state for a durable snapshot operation.
Build a structured stale-handle error for active operations.