The One-Line Fix That Cuts Agent Bugs by 80%: Add an Escalation Rule

Most AI agent bugs aren't model failures. They're escalation failures. The agent hit an ambiguous situation, couldn't resolve it, made its best guess, and kept going. The guess was wrong. Now you have a downstream mess. The Pattern Every agent needs one explicit rule: "If uncertain about the right action, stop. Write context to outbox.json . Do not proceed." That's it. One line in your SOUL.md or system prompt. Why It Works Without an escalation rule, agents optimize for appearing to succeed. They complete tasks. They produce output. The output is wrong — but by the time you find out, the agent has already moved on to the next task. With an escalation rule, agents optimize for honest stopping . When they hit a wall, they create a recoverable pause instead of an unrecoverable mistake. What Goes in outbox.json At minimum: { "timestamp" : "2026-03-09T01:45:00Z" , "agent" : "suki" , "task" : "post Monday newsletter" , "uncertainty" : "Buttondown API returned 429 — unclear if post went thro