← Latest papers
🤖 AI

Repair the Amplifier, Not the Symptom: Stable World-Model Correction for Agent Rollouts

This paper introduces WM-SAR, a world-model corrector that outperforms traditional symptom-scanning approaches by identifying and repairing the specific causal subgraph responsible for amplifying errors in large agent planning graphs, thereby enabling efficient in-place stabilization without the computational cost of full-graph replanning.

Original authors: Xinyuan Song, Zekun Cai

Published 2026-07-03
📖 4 min read☕ Coffee break read

Original authors: Xinyuan Song, Zekun Cai

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are the captain of a massive spaceship (an AI agent) trying to navigate a complex galaxy. Your ship doesn't just move in a straight line; it builds a giant, branching map of its journey, with thousands of stops, tool uses, and checks along the way. This map is called a planning graph.

Sometimes, the ship makes a mistake. Maybe it picks the wrong fuel, misreads a star chart, or forgets a rule. In the past, when the ship messed up, the standard fix was to throw away the entire map and try to redraw the whole journey from scratch.

The authors of this paper say: "Stop doing that!"

They argue that redrawing the whole map is a waste of fuel (computational power) and time. It's like throwing away a whole book because you misspelled one word on page 50. Instead, you should find the specific broken part and fix just that.

Here is the problem: Where exactly is the broken part?

The Trap of "Visible Symptoms"

Most current repair methods act like a doctor who only treats the fever.

  • The Scenario: The ship's engine overheats (the visible symptom) because a tiny valve in the fuel line was installed backward three hours ago (the root cause).
  • The Old Way: The "Engineering" repair method scans the map, sees the hot engine, and says, "Ah, the engine is broken! Let's fix the engine." It patches the engine.
  • The Result: The engine cools down for a moment, but because the backward valve is still there, the engine overheats again on the next leg of the trip. The ship is still broken; you just treated the symptom, not the disease.

The New Solution: WM-SAR (The "Amplifier" Detector)

The authors propose a new method called WM-SAR. Instead of looking for the thing that looks the most broken, WM-SAR looks for the thing that makes the whole system unstable.

Think of it like a sound system with a microphone too close to a speaker.

  • The Symptom: The speakers are screeching loudly (high error).
  • The Old Fix: You turn down the volume on the speakers. The screech stops for a second, but as soon as you turn it back up, it screeches again because the microphone is still too close.
  • The WM-SAR Fix: This method asks, "What is amplifying the noise?" It identifies the feedback loop between the mic and the speaker. It doesn't just turn down the volume; it moves the microphone. Once the feedback loop is broken, the system becomes stable, even if the speakers were the loudest part.

How WM-SAR Works (The "Backward" Search)

  1. Look for the Amplifier: Instead of scanning the map from start to finish, WM-SAR works backward from the failure. It asks: "Which small group of connected steps is responsible for repeating this error?"
  2. Find the "Causal Subgraph": It isolates a tiny, connected chain of events (like the backward valve and the fuel pump) that, if fixed, stops the error from growing.
  3. Send a Tiny Note to the AI: Instead of showing the AI the entire 10,000-step map (which confuses it and wastes memory), WM-SAR sends only that tiny, broken chain to the AI.
  4. The AI Fixes It: The AI looks at this clean, focused slice of the problem, figures out the root cause, and fixes it.

Why This Matters

The paper tested this on simulated agent tasks (like software debugging and web navigation). They found that:

  • Old methods often fixed the wrong thing or had to look at the whole map to get lucky.
  • WM-SAR fixed the problem using much less information (fewer "tokens" or words).
  • Stability: After WM-SAR fixed the problem, the agent didn't just survive the next step; it stayed stable for hundreds of future steps. The error didn't come back.

The Bottom Line

The paper's main message is: Don't just repair the symptom; repair the amplifier.

If you want to fix a complex AI agent, don't just patch the part that is currently screaming. Find the small, hidden connection that is making the whole system scream, fix that, and the rest of the system will calm down on its own. This saves time, saves money, and makes the AI much more reliable.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →