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.
I haven't used Conductor, but quickly looking at the README, Conductor lets you define JSON workflows to orchestrate existing microservices. By contrast, DBOS helps you build highly reliable applications--it runs as a library inside your program and helps you build durable workflows that run alongside your code and are written in the same language.
The moment you rely on LLM to be a guardrail, well you are risking it to fail.
reply