Module exec_state 

ExecState — per-poll execution-state bundle (frontier, slot table, pending state, scheduler, inbound contexts, monotonic ID allocator). Owned by Engine as one field. ExecState — the engine’s per-poll execution-state bundle.

Groups the fields that walk the DAG cascade together: the frontier work queue, the slot table, per-execution liveness, parked async ops, in-cycle completions, function-call invocation frames, and the monotonic ID allocator.

Engine carries one exec: ExecState field rather than nine sibling fields. The architectural grouping matches the poll cycle: frontier drains seed downstream ops while completions match against parked async suspensions.

The timer scheduler and inbound-envelope context map live on crate::framework::FrameworkComponents alongside the other syscall-driven primitives (HoldTable, SerializeQueue, RecordBuffer, EventSource). Syscalls (Sleep, Interval, Pulse) drive the scheduler; RX gates + wire.Send forwarding drive inbound context lookup. Treating them as framework primitives matches their consumers.

Structs

ExecState

Per-poll execution-state bundle held on Engine.

IdAllocator

Monotonic per-Node ID source. Single-threaded reads/writes so the ingress queue stays the only cross-thread sync primitive.