Late-Bound Sagas: Why Your Agent Is Not an LLM in a Loop
1–2 of 2 posts
Re: Late-Bound Sagas: Why Your Agent Is Not an LLM in a Loop
#2Author here, built Netflix Conductor.
The post is three arguments that together form a new framing for agent runtimes:
The LLM shouldn't execute anything (planning and execution belong on strictly separated planes), signals are the primitive that makes out-of-band cancellation and replanning possible, and the workflow's graph should be synthesized by the LLM at runtime rather than declared by a programmer at commit time. That last one is the load-bearing idea - a Late-Bound Saga.
Agentspan is the runtime that implements it on top of Conductor. Happy to answer about any of these and why I think the `while` loop is the wrong primitive.