Struct TaskLaunchService 

pub struct TaskLaunchService { /* private fields */ }

Domain service that compiles, links, and runs a Blueprint’s flow to completion through the Engine. See the module doc for the full responsibility list.

Implementations

impl TaskLaunchService

pub fn new(engine: Engine, compiler: Compiler) -> Self

Build a service bound to one Engine and one Compiler.

pub fn with_externs(self, externs: Arc<dyn Externs + Send + Sync>) -> Self

Replace the call_extern registry (builder style). Entries MUST be pure functions — no side effects, no flow control; effectful work belongs to Step / agents, not externs (flow-ir canonical contract).

pub fn with_binding_provider( self, provider: Arc<dyn AgentBindingProvider>, ) -> Self

Inject the execution-environment binding provider. Platform plugins and Operator/MainAI implementations use this same interface; Core retains receipt validation and digest ownership.

pub fn with_legacy_worker_binding_policy( self, policy: LegacyWorkerBindingPolicy, ) -> Self

Configure the migration gate for deprecated profile.worker_binding.

pub fn engine(&self) -> &Engine

The bound Engine.

pub fn compiler(&self) -> &Compiler

The bound Compiler.

pub async fn launch( &self, input: TaskLaunchInput, ) -> Result<TaskLaunchOutput, TaskLaunchError>

Run the Blueprint’s flow to completion and return the final ctx.

Failure paths:

• compiler.compile failure → TaskLaunchError::Compile.
• engine.attach failure → TaskLaunchError::Engine.
• A Step inside flow eval producing a dispatcher error, or a sub-flow raising, → TaskLaunchError::FlowEval. There is no silent partial-success completion; failures always propagate.