The Execution Guard Pattern for AI Agents

AI agents don’t just think — they execute real-world actions. Payments. Trades. Emails. API calls. And under retries, timeouts, or crashes… they can execute the same action twice. Not because the model was wrong — because the system has no memory of execution. The hidden failure mode A typical failure path looks like this: agent decides to call tool → tool executes side effect → response is lost (timeout / crash / disconnect) → system retries → side effect executes again Now you have: duplicate payments duplicate trades duplicate emails duplicate API mutations Not because the decision was wrong — because the execution layer has no durable receipt. Retries are correct — and still dangerous Retries are necessary for reliability. But retries + irreversible side effects without a guard = replay risk. The system cannot confidently answer: “Did this action already happen?” So it does the only thing it can: → tries again That’s fine for reads. It’s dangerous for writes. The Execution Guard Pa