Skip to main content
Run two independent fixture reads and a dependent sum through a versioned host catalog. Invoke the completed task again and verify that all three callback results are retained. No provider, database or external service is called.

Get the project

Download the complete TypeScript project. This archive targets Agentium 4.9.0 and installs matching published core/harness packages. The project includes source, dependencies, a compiler configuration and run instructions; see installation for runtime requirements. For a manual project, install the matching core/harness packages plus zod, typescript, tsx and @types/node; set "type": "module" in package.json. Save as execution-graph.ts:
execution-graph.ts

Run and inspect the outcome

The command prints a completed task, the three expected output fields, three dispatches after retained result, and persistent store: false. The second worker retrieves the completed output without reserving new dispatch attempts. inspect(key) can read evidence without claiming or mutating the task. References infer data dependencies. The catalog declares exact permitted input/output paths and validates future-value templates, then the runtime resolves and validates actual values before dispatch. Explicit root limits cap concurrency, unique node incarnations, work attempts and revisions. The fixture permits zero model calls and exactly three tool calls.

Adapt the binding and store

This fixture proves local completed-task reuse, not a process-crash or external-effect guarantee. Persistent adapters need their own failure-window tests. Cancellation does not undo accepted work, and fencing cannot physically stop a remote request. Follow the recoverable graph guide before connecting a durable backend or effect destination. The fixture owns no network clients or persistent data. Hosts own the lifecycle of a persistent store and shared providers; ExecutionGraphRuntime has no general store-close method. Next, compare ordinary Workflow graphs or add bounded planning.