Expand description
In-memory runtime implementation of the shared async-operation lifecycle seam.
Per-operation canonical lifecycle state lives in the MeerkatMachine DSL
authority (op_statuses, op_terminal_outcomes, op_kinds,
op_sources, op_peer_ready, op_progress_counts, active_op_count,
wait_active, wait_operation_ids). This shell layer owns pure mechanics: watcher
channels, timestamps, peer handles, snapshot assembly, FIFO eviction
bookkeeping, the completion feed buffer, and typed delivery of generated
admission/rejection feedback.
Per-transition legality (“is CompleteOp legal on a Provisioning op?”)
is NOT owned by the shell — it lives in the DSL’s from_status_valid
guards on each op-lifecycle transition. The shell’s only job on a
GuardRejected rejection is to ask the generated rejection resolver for
the public result class.
Structs§
- Completion
Feed Canonical State - Generated-owned public completion feed fact captured from DSL authority.
- Operation
Canonical State - Canonical per-operation state as captured in persisted snapshots.
- OpsLifecycle
Config - Configuration for
RuntimeOpsLifecycleRegistry. - OpsLifecycle
Persistence Request - Persisted
OpsSnapshot - Serializable snapshot of the ops lifecycle registry state.
- Registry
Canonical State - Canonical registry-level state as captured in persisted snapshots.
- Runtime
Completion Feed - Read-only handle to the runtime completion feed.
- Runtime
OpsLifecycle Registry - Per-runtime shared registry for async operation lifecycle truth.