Documentation
¶
Overview ¶
Command embed is the Tier-A example main from the flows design (§18.6): it EMBEDS the engine as a plain library — zero third-party dependencies, no service, no control plane — and drives one run end to end in-process.
The pattern it proves (copy-paste-able): build a small Graph[S] in main(), Compile it once with an in-memory CheckpointStore, Run it from an initial state, and — when a vertex Interrupts (human-in-the-loop) — Resume it by id with a payload, all in the SAME process against the SAME store. This is the in-process embed story: no HTTP, no registry, no worker loop.
To keep the demo deterministic and testable WITHOUT binding a port or hanging, the wiring lives in a factored run(ctx) that main() simply calls and reports. The graph is a tiny three-vertex pipeline that pauses once for "approval" and then completes:
greet ──▶ approve ──▶ deliver
(Interrupts on the first pass; Resume(payload) feeds the
approval and the run routes on to deliver → finish)
Source Files