feat(engine): substrate-neutral execution engine abstraction
Introduce the swactor engine: a swactor-owned composite that retains a
selected execution substrate, drives the core runtime, and hosts the
async/blocking/timer work that backs actors. Integrations receive one
cloneable EngineHandle and never construct or borrow a raw Tokio
runtime/handle.
Engine crate (crates/engine):
- The contract: spawn / spawn_blocking / timer / interval / now, a
per-implementation capability model with construction-time binding
(require()), and engine-owned time. The engine owns all progression;
actor handlers stay synchronous and never .await.
- TokioBackend owns the Tokio runtime and schedules core ticks and
supporting futures on it; SteppingBackend is a single-threaded
deterministic scheduler with virtual time (the non-Tokio portability
proof). Core is driven through its existing tick() surface; a
self-rescheduling CoreDriver is installed at construction and is the
sole place permitted to call try_tick.
iroh-driver:
- Receives an EngineHandle instead of a raw Tokio Handle. Accepts,
reads, dials, writes, endpoint construction, and teardown schedule
through it; required capabilities (tasks/timers/io) are validated
before the endpoint binds. Engine-hosted interval pumps drive
actor-bridge, datastream, and edge ingress.
myelin:
- One node/orchestrator engine owns core, protocol tick injection, and
transport progression; the application loop only drains
integration-owned queues. Stage-shard process readers, delayed actor
messages, helper stdout/stderr, prompt RPC, and CPU sampling all
schedule through the engine (spawn_blocking / engine tasks / timers).
- Removed the split-engine APIs: install_actor_bridge_pump(period) and
spawn_protocol_ticker(period) use each component's stored engine;
deleted the no-op pump_network callback and its plumbing; deleted the
dashboard raw-Tokio/standalone-runtime conveniences.
Enforcement:
- A clippy disallowed-methods boundary forbids direct runtime/scheduling/
time/core-driving bypasses, denied in swactor-engine, iroh-driver, and
myelin. Retained excluded uses (VastAI provider, provider process
supervision/log capture, OS-signal/stdin/process-control sequencing)
carry narrow allowances with reasons.
Verification:
- Engine contract + unit tests (incl. the SteppingBackend portability
proof), iroh integration tests (capability rejection before binding,
multi-node actor behavior), and a production execution-composition
smoke test that observes engine-driven actor progress with no ambient
Tokio runtime and no manual tick/pump. Workspace all-target/all-feature
clippy and tests are green.
Specs co-located with their crates: ENGINE_SPEC.md in crates/engine,
IROH_DRIVER_SPEC.md in crates/iroh-driver. VastAI remains explicitly out
of scope pending its separate redesign.
2026-08-10 20:23:03 +00:00
|
|
|
//! Execution backend SPI.
|
|
|
|
|
//!
|
|
|
|
|
//! The [`ExecutionBackend`] trait is an implementation seam the engine uses to
|
|
|
|
|
//! schedule work and read engine time. It is not the interface applications
|
|
|
|
|
//! consume; that is [`crate::EngineHandle`]. A native implementation erases
|
|
|
|
|
//! tasks once when they are installed; this representation is not a
|
|
|
|
|
//! cross-target requirement (see `ENGINE_SPEC.md`).
|
|
|
|
|
|
|
|
|
|
use std::pin::Pin;
|
|
|
|
|
use std::time::Duration;
|
|
|
|
|
|
|
|
|
|
use crate::time::EngineInstant;
|
|
|
|
|
|
|
|
|
|
/// A boxed, sendable future returned by the engine substrate.
|
|
|
|
|
pub type BoxTask = Pin<Box<dyn Future<Output = ()> + Send + 'static>>;
|
|
|
|
|
/// A boxed, sendable timer future produced by the substrate.
|
|
|
|
|
pub type BoxTimer = Pin<Box<dyn Future<Output = ()> + Send + 'static>>;
|
|
|
|
|
/// A boxed, sendable one-shot blocking workload.
|
|
|
|
|
pub type BoxWork = Box<dyn FnOnce() + Send + 'static>;
|
|
|
|
|
|
|
|
|
|
/// The substrate-specific execution surface an engine schedules onto.
|
|
|
|
|
///
|
|
|
|
|
/// Object-safe so the composite [`Engine`](crate::Engine) can store it as
|
|
|
|
|
/// `Arc<dyn ExecutionBackend>` without being generic over the backend.
|
|
|
|
|
pub trait ExecutionBackend: Send + Sync + 'static {
|
|
|
|
|
/// Schedule `task` to run as cooperative engine work.
|
|
|
|
|
fn spawn(&self, task: BoxTask);
|
|
|
|
|
/// Schedule `work` on a dedicated blocking thread.
|
|
|
|
|
fn spawn_blocking(&self, work: BoxWork);
|
|
|
|
|
/// Produce a future that completes after `delay`.
|
|
|
|
|
fn timer(&self, delay: Duration) -> BoxTimer;
|
|
|
|
|
/// Read the engine's monotonic clock.
|
|
|
|
|
fn now(&self) -> EngineInstant;
|
|
|
|
|
/// Report the substrate's advertised capabilities.
|
|
|
|
|
fn capabilities(&self) -> Capabilities;
|
2026-08-16 13:27:38 +00:00
|
|
|
/// How long the core driver parks between ticks when its worker is idle.
|
|
|
|
|
///
|
|
|
|
|
/// `Duration::ZERO` (the default) re-arms the driver immediately after
|
|
|
|
|
/// every tick — a poll loop at scheduler speed. Backends with real timers
|
|
|
|
|
/// return a small interval so an idle core parks instead of spinning;
|
|
|
|
|
/// newly delivered work is observed within one interval. Every poll still
|
|
|
|
|
/// runs one tick, so this only bounds idle wakeup latency.
|
|
|
|
|
fn core_idle_poll(&self) -> Duration {
|
|
|
|
|
Duration::ZERO
|
|
|
|
|
}
|
feat(engine): substrate-neutral execution engine abstraction
Introduce the swactor engine: a swactor-owned composite that retains a
selected execution substrate, drives the core runtime, and hosts the
async/blocking/timer work that backs actors. Integrations receive one
cloneable EngineHandle and never construct or borrow a raw Tokio
runtime/handle.
Engine crate (crates/engine):
- The contract: spawn / spawn_blocking / timer / interval / now, a
per-implementation capability model with construction-time binding
(require()), and engine-owned time. The engine owns all progression;
actor handlers stay synchronous and never .await.
- TokioBackend owns the Tokio runtime and schedules core ticks and
supporting futures on it; SteppingBackend is a single-threaded
deterministic scheduler with virtual time (the non-Tokio portability
proof). Core is driven through its existing tick() surface; a
self-rescheduling CoreDriver is installed at construction and is the
sole place permitted to call try_tick.
iroh-driver:
- Receives an EngineHandle instead of a raw Tokio Handle. Accepts,
reads, dials, writes, endpoint construction, and teardown schedule
through it; required capabilities (tasks/timers/io) are validated
before the endpoint binds. Engine-hosted interval pumps drive
actor-bridge, datastream, and edge ingress.
myelin:
- One node/orchestrator engine owns core, protocol tick injection, and
transport progression; the application loop only drains
integration-owned queues. Stage-shard process readers, delayed actor
messages, helper stdout/stderr, prompt RPC, and CPU sampling all
schedule through the engine (spawn_blocking / engine tasks / timers).
- Removed the split-engine APIs: install_actor_bridge_pump(period) and
spawn_protocol_ticker(period) use each component's stored engine;
deleted the no-op pump_network callback and its plumbing; deleted the
dashboard raw-Tokio/standalone-runtime conveniences.
Enforcement:
- A clippy disallowed-methods boundary forbids direct runtime/scheduling/
time/core-driving bypasses, denied in swactor-engine, iroh-driver, and
myelin. Retained excluded uses (VastAI provider, provider process
supervision/log capture, OS-signal/stdin/process-control sequencing)
carry narrow allowances with reasons.
Verification:
- Engine contract + unit tests (incl. the SteppingBackend portability
proof), iroh integration tests (capability rejection before binding,
multi-node actor behavior), and a production execution-composition
smoke test that observes engine-driven actor progress with no ambient
Tokio runtime and no manual tick/pump. Workspace all-target/all-feature
clippy and tests are green.
Specs co-located with their crates: ENGINE_SPEC.md in crates/engine,
IROH_DRIVER_SPEC.md in crates/iroh-driver. VastAI remains explicitly out
of scope pending its separate redesign.
2026-08-10 20:23:03 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Capabilities an execution backend advertises.
|
|
|
|
|
///
|
|
|
|
|
/// - `tasks`: cooperative task scheduling.
|
|
|
|
|
/// - `timers`: timer and interval support.
|
|
|
|
|
/// - `blocking`: dedicated blocking-thread pools.
|
|
|
|
|
/// - `io`: asynchronous I/O reactor (e.g. Tokio's I/O driver from `enable_all`).
|
|
|
|
|
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
|
|
|
|
|
pub struct Capabilities {
|
|
|
|
|
pub tasks: bool,
|
|
|
|
|
pub timers: bool,
|
|
|
|
|
pub blocking: bool,
|
|
|
|
|
pub io: bool,
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
impl Capabilities {
|
|
|
|
|
/// Convenience: only baseline task execution.
|
2026-08-16 13:27:38 +00:00
|
|
|
pub const TASKS_ONLY: Self = Self {
|
|
|
|
|
tasks: true,
|
|
|
|
|
timers: false,
|
|
|
|
|
blocking: false,
|
|
|
|
|
io: false,
|
|
|
|
|
};
|
feat(engine): substrate-neutral execution engine abstraction
Introduce the swactor engine: a swactor-owned composite that retains a
selected execution substrate, drives the core runtime, and hosts the
async/blocking/timer work that backs actors. Integrations receive one
cloneable EngineHandle and never construct or borrow a raw Tokio
runtime/handle.
Engine crate (crates/engine):
- The contract: spawn / spawn_blocking / timer / interval / now, a
per-implementation capability model with construction-time binding
(require()), and engine-owned time. The engine owns all progression;
actor handlers stay synchronous and never .await.
- TokioBackend owns the Tokio runtime and schedules core ticks and
supporting futures on it; SteppingBackend is a single-threaded
deterministic scheduler with virtual time (the non-Tokio portability
proof). Core is driven through its existing tick() surface; a
self-rescheduling CoreDriver is installed at construction and is the
sole place permitted to call try_tick.
iroh-driver:
- Receives an EngineHandle instead of a raw Tokio Handle. Accepts,
reads, dials, writes, endpoint construction, and teardown schedule
through it; required capabilities (tasks/timers/io) are validated
before the endpoint binds. Engine-hosted interval pumps drive
actor-bridge, datastream, and edge ingress.
myelin:
- One node/orchestrator engine owns core, protocol tick injection, and
transport progression; the application loop only drains
integration-owned queues. Stage-shard process readers, delayed actor
messages, helper stdout/stderr, prompt RPC, and CPU sampling all
schedule through the engine (spawn_blocking / engine tasks / timers).
- Removed the split-engine APIs: install_actor_bridge_pump(period) and
spawn_protocol_ticker(period) use each component's stored engine;
deleted the no-op pump_network callback and its plumbing; deleted the
dashboard raw-Tokio/standalone-runtime conveniences.
Enforcement:
- A clippy disallowed-methods boundary forbids direct runtime/scheduling/
time/core-driving bypasses, denied in swactor-engine, iroh-driver, and
myelin. Retained excluded uses (VastAI provider, provider process
supervision/log capture, OS-signal/stdin/process-control sequencing)
carry narrow allowances with reasons.
Verification:
- Engine contract + unit tests (incl. the SteppingBackend portability
proof), iroh integration tests (capability rejection before binding,
multi-node actor behavior), and a production execution-composition
smoke test that observes engine-driven actor progress with no ambient
Tokio runtime and no manual tick/pump. Workspace all-target/all-feature
clippy and tests are green.
Specs co-located with their crates: ENGINE_SPEC.md in crates/engine,
IROH_DRIVER_SPEC.md in crates/iroh-driver. VastAI remains explicitly out
of scope pending its separate redesign.
2026-08-10 20:23:03 +00:00
|
|
|
|
|
|
|
|
/// Convenience: every capability.
|
2026-08-16 13:27:38 +00:00
|
|
|
pub const ALL: Self = Self {
|
|
|
|
|
tasks: true,
|
|
|
|
|
timers: true,
|
|
|
|
|
blocking: true,
|
|
|
|
|
io: true,
|
|
|
|
|
};
|
feat(engine): substrate-neutral execution engine abstraction
Introduce the swactor engine: a swactor-owned composite that retains a
selected execution substrate, drives the core runtime, and hosts the
async/blocking/timer work that backs actors. Integrations receive one
cloneable EngineHandle and never construct or borrow a raw Tokio
runtime/handle.
Engine crate (crates/engine):
- The contract: spawn / spawn_blocking / timer / interval / now, a
per-implementation capability model with construction-time binding
(require()), and engine-owned time. The engine owns all progression;
actor handlers stay synchronous and never .await.
- TokioBackend owns the Tokio runtime and schedules core ticks and
supporting futures on it; SteppingBackend is a single-threaded
deterministic scheduler with virtual time (the non-Tokio portability
proof). Core is driven through its existing tick() surface; a
self-rescheduling CoreDriver is installed at construction and is the
sole place permitted to call try_tick.
iroh-driver:
- Receives an EngineHandle instead of a raw Tokio Handle. Accepts,
reads, dials, writes, endpoint construction, and teardown schedule
through it; required capabilities (tasks/timers/io) are validated
before the endpoint binds. Engine-hosted interval pumps drive
actor-bridge, datastream, and edge ingress.
myelin:
- One node/orchestrator engine owns core, protocol tick injection, and
transport progression; the application loop only drains
integration-owned queues. Stage-shard process readers, delayed actor
messages, helper stdout/stderr, prompt RPC, and CPU sampling all
schedule through the engine (spawn_blocking / engine tasks / timers).
- Removed the split-engine APIs: install_actor_bridge_pump(period) and
spawn_protocol_ticker(period) use each component's stored engine;
deleted the no-op pump_network callback and its plumbing; deleted the
dashboard raw-Tokio/standalone-runtime conveniences.
Enforcement:
- A clippy disallowed-methods boundary forbids direct runtime/scheduling/
time/core-driving bypasses, denied in swactor-engine, iroh-driver, and
myelin. Retained excluded uses (VastAI provider, provider process
supervision/log capture, OS-signal/stdin/process-control sequencing)
carry narrow allowances with reasons.
Verification:
- Engine contract + unit tests (incl. the SteppingBackend portability
proof), iroh integration tests (capability rejection before binding,
multi-node actor behavior), and a production execution-composition
smoke test that observes engine-driven actor progress with no ambient
Tokio runtime and no manual tick/pump. Workspace all-target/all-feature
clippy and tests are green.
Specs co-located with their crates: ENGINE_SPEC.md in crates/engine,
IROH_DRIVER_SPEC.md in crates/iroh-driver. VastAI remains explicitly out
of scope pending its separate redesign.
2026-08-10 20:23:03 +00:00
|
|
|
|
|
|
|
|
/// Convenience: no capabilities. Reported by an [`EngineHandle`](crate::EngineHandle)
|
|
|
|
|
/// whose owning engine has been dropped (ENGINE_SPEC.md).
|
2026-08-16 13:27:38 +00:00
|
|
|
pub const NONE: Self = Self {
|
|
|
|
|
tasks: false,
|
|
|
|
|
timers: false,
|
|
|
|
|
blocking: false,
|
|
|
|
|
io: false,
|
|
|
|
|
};
|
feat(engine): substrate-neutral execution engine abstraction
Introduce the swactor engine: a swactor-owned composite that retains a
selected execution substrate, drives the core runtime, and hosts the
async/blocking/timer work that backs actors. Integrations receive one
cloneable EngineHandle and never construct or borrow a raw Tokio
runtime/handle.
Engine crate (crates/engine):
- The contract: spawn / spawn_blocking / timer / interval / now, a
per-implementation capability model with construction-time binding
(require()), and engine-owned time. The engine owns all progression;
actor handlers stay synchronous and never .await.
- TokioBackend owns the Tokio runtime and schedules core ticks and
supporting futures on it; SteppingBackend is a single-threaded
deterministic scheduler with virtual time (the non-Tokio portability
proof). Core is driven through its existing tick() surface; a
self-rescheduling CoreDriver is installed at construction and is the
sole place permitted to call try_tick.
iroh-driver:
- Receives an EngineHandle instead of a raw Tokio Handle. Accepts,
reads, dials, writes, endpoint construction, and teardown schedule
through it; required capabilities (tasks/timers/io) are validated
before the endpoint binds. Engine-hosted interval pumps drive
actor-bridge, datastream, and edge ingress.
myelin:
- One node/orchestrator engine owns core, protocol tick injection, and
transport progression; the application loop only drains
integration-owned queues. Stage-shard process readers, delayed actor
messages, helper stdout/stderr, prompt RPC, and CPU sampling all
schedule through the engine (spawn_blocking / engine tasks / timers).
- Removed the split-engine APIs: install_actor_bridge_pump(period) and
spawn_protocol_ticker(period) use each component's stored engine;
deleted the no-op pump_network callback and its plumbing; deleted the
dashboard raw-Tokio/standalone-runtime conveniences.
Enforcement:
- A clippy disallowed-methods boundary forbids direct runtime/scheduling/
time/core-driving bypasses, denied in swactor-engine, iroh-driver, and
myelin. Retained excluded uses (VastAI provider, provider process
supervision/log capture, OS-signal/stdin/process-control sequencing)
carry narrow allowances with reasons.
Verification:
- Engine contract + unit tests (incl. the SteppingBackend portability
proof), iroh integration tests (capability rejection before binding,
multi-node actor behavior), and a production execution-composition
smoke test that observes engine-driven actor progress with no ambient
Tokio runtime and no manual tick/pump. Workspace all-target/all-feature
clippy and tests are green.
Specs co-located with their crates: ENGINE_SPEC.md in crates/engine,
IROH_DRIVER_SPEC.md in crates/iroh-driver. VastAI remains explicitly out
of scope pending its separate redesign.
2026-08-10 20:23:03 +00:00
|
|
|
|
|
|
|
|
/// Whether `self` satisfies every capability marked `true` in `required`.
|
|
|
|
|
///
|
|
|
|
|
/// A `required` field set to `false` is treated as "not required" — the
|
|
|
|
|
/// backend may or may not provide it. Used by
|
|
|
|
|
/// [`EngineHandle::require`](crate::EngineHandle::require) to validate
|
|
|
|
|
/// integration requirements (ENGINE_SPEC.md).
|
|
|
|
|
pub fn satisfies(&self, required: Capabilities) -> bool {
|
|
|
|
|
(!required.tasks || self.tasks)
|
|
|
|
|
&& (!required.timers || self.timers)
|
|
|
|
|
&& (!required.blocking || self.blocking)
|
|
|
|
|
&& (!required.io || self.io)
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Errors that can arise while constructing an engine.
|
|
|
|
|
#[derive(Debug, Clone)]
|
|
|
|
|
pub enum EngineError {
|
|
|
|
|
/// A capability required by the engine is not advertised by the backend.
|
|
|
|
|
MissingRequiredCapability,
|
|
|
|
|
/// A backend-owned substrate could not be constructed (e.g. a Tokio
|
|
|
|
|
/// runtime failed to build).
|
|
|
|
|
BackendSetup(String),
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
impl std::fmt::Display for EngineError {
|
|
|
|
|
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
|
|
|
|
|
match self {
|
|
|
|
|
EngineError::MissingRequiredCapability => {
|
|
|
|
|
write!(f, "backend is missing a capability required by the engine")
|
|
|
|
|
}
|
|
|
|
|
EngineError::BackendSetup(msg) => {
|
|
|
|
|
write!(f, "backend substrate setup failed: {msg}")
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
impl std::error::Error for EngineError {}
|