Saga Pattern

How to treat a multi-step coding agent run as a distributed transaction: pair each tool with a compensation, log every intent before the call runs, hold irreversible calls in an outbox until the run succeeds, and send corrections to the people who saw a change that got reverted.

You'll learn how to spot when a saga across services is actually hiding a bad bounded-context split, and how to test whether a given saga is justified or just compensating for a broken service boundary.

The bug wasn't a hallucination and it wasn't sloppy prompting — it was a structural gap between what the agent believed about the saga's state and what was actually true, and no amount of better prompting closes that gap.