What does cascading error compounding mean for production agent design and reliability budgeting?
A production agent has 90% per-step reliability on a 10-step task. Calculate the end to end success rate and explain the engineering implications for production threshold design and task length.
Step reliability multiplies, so end to end success is roughly p^N. At 90% per step over 10 steps that is only 35%, which is why long agent horizons collapse.
Imagine a relay race where one runner must hand a baton to the next, ten times in a row, and each handoff works 9 times out of 10. That sounds reliable. But the baton only finishes the whole race if every single handoff succeeds, and one fumble anywhere ruins the run. Multiply the odds: nine-tenths, ten times over, and you land near a third. So the team that wins almost every handoff still drops the baton most races. An agent is the same relay. Each step is a handoff, and the whole task only counts as done if no step failed. The more handoffs you chain together, the worse the finish line looks, even when each individual runner is good. That is why builders keep agent tasks short and add ways to recover a dropped baton.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
Open with the p to the N model and compute 0.9 to the tenth as 35 percent. Invert it to show the 98.9 percent per-step requirement for a 90 percent target. Then walk the three levers, raising per-step reliability, shortening the horizon, and adding recovery, and close on the cost and latency tradeoffs that recovery introduces.
Real products, models, and research that use this idea.
- SWE-bench agents built on Claude Opus 4.7 and GPT-5.5 chain many edit, run, and debug steps, and their solve rates show exactly this compounding, which is why frontier coding agents add test-driven verification between steps.
- Devin and Cursor break long coding tasks into short verify and retry segments rather than one long trajectory, so a failed step reruns instead of dumping the whole run.
- LangGraph and the Anthropic SDK expose retry, checkpoint, and human in the loop interrupt primitives precisely so builders can reset error accumulation between segments.
- Observability tools like Langfuse and Arize attribute failures per step, letting teams find the weakest step whose per-step rate is dragging the product down.
What an interviewer would ask next. Try answering before peeking at the approach.
QYour agent has one weak step at 70% and nine strong steps at 99%. Where should you spend engineering effort, and why?
QHow does adding a verify and retry wrapper around each step change the effective per-step reliability in the p^N formula?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Quoting a high per-step accuracy as if it were the task success rate. A 90% step over ten steps is 35% end to end, not 90%, because the errors compound.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.