DEV Community

Marc Duiker for Diagrid

Posted on

Durable Execution, Now Built for Agents

Durable execution has become an expectation for agent workloads. If the process dies halfway through a refund, the run resumes at the last completed step instead of re-issuing it. What it does not give you is proof. Replaying a run is not the same as proving what ran.

The missing piece is verifiability

Verifiable execution is a record of what ran, in what order, and what it produced, where every LLM call, tool call and decision is cryptographically signed and traceable to its source. Durability keeps work alive. Verifiability makes it checkable by someone who was not there.

More autonomy, less reproducibility

In a deterministic workflow the steps live in your code. You can diff them and point at the line that made a decision. As you hand control to the model, that structure moves out of the code and into the run itself. The model picks which tools to call and in what order, so two runs on the same input can take different paths, and nothing in your repository records which path a given run took.

Most teams make that trade on purpose. The flexibility is what lets an agent settle a messy dispute that no if-statement anticipated. The cost arrives later, when someone asks why a particular refund was denied. A stack trace tells you what your code did. It cannot tell you why the model chose one tool over another, and re-running the agent produces a fresh set of decisions rather than the ones you need to account for.

So the structure you take out of your code has to reappear underneath it, as a record rather than as more branching logic: every call the agent made, in order, with the inputs and outputs that led to the next step, each entry signed so it can be verified later.

What Catalyst is built for

Declarative workflow engines, where the flow lives outside your code, do not integrate natively with agent frameworks. Code-first engines integrate, but leave the run unverifiable, so you can resume it without being able to prove it. Agentic durable execution takes a third route: keep the framework you already use and make its execution durable and verifiable.

That is what Diagrid Catalyst is built for. Add a package to LangGraph, Microsoft Agent Framework, Google ADK, AWS Strands, OpenAI Agents SDK or CrewAI, and you get durable and verifiable execution through workflows, attestation, cryptographic signing, and SPIFFE-based workload identity.

Durable execution is becoming table stakes for agents. Verifiable execution is what makes them trusted.

Read the full post on diagrid.io to learn more.

Top comments (0)