/p/2026-10-18 · explainer
Paper explainer · 2610.21514 · Skarich

The hypothesis is survivable. The plan is not.

A repair agent forms an idea about how the code works, turns it into an implementation plan, then writes a patch. Hand it a specific wrong idea — the wrong invariant, the wrong place to hold state — and where that idea sits decides almost everything. Over 1,844 requests on two deliberately constructed Python tasks, the same misconception failed 21.9% of attempts from the hypothesis and 54.7% from the plan on one task, and 53.4% against 83.0% on the other. Adding the matching wrong hypothesis on top of a plan that already carried it bought almost nothing.

01 · The problem

A red test tells you it failed, not which decision did it

which task the agent was given

02 · The mechanism

The plan is the last place the idea can be stopped

where the wrong idea was placed

03 · The evidence

Drop any model, drop any misconception, the gap stays

which task

04 · Why I care

Every misconception breaks the same thing twice

which wrong idea the plan carried

05 · Apply it

Your repair loop, and where you put the gate illustrative

where you spend the review

Results

What the paper actually measured

What it does not show

In practice