Plans Are Not Executions: Adapting Frozen World-Model Planners to Controller-Induced Execution Shift

Introduction to the show: ident: Robotics Radio. Generated commentary on the latest robotics and control papers.

Rosa: Today's paper: "Plans Are Not Executions".

Dev: The gist: ExecutionBridge, which infers controller-specific execution characteristics from planned–executed trajectory pairs and uses them to adapt the native ego latent rollout while keeping the original planned trajectory unchanged,

Rosa: First, who's behind it and why it matters.

Title and authors: Rosa: The paper is called "Plans Are Not Executions: Adapting Frozen World-Model Planners to Controller-Induced Execution Shift" by Danqi Zhao, Keyu Chen, Wenchao Sun, Minglei Huang, Jianhe Zhang, Yan Zhu, Hao Cheng, Zifan Cao and Sifa Zheng.

Dev: It’s interesting because the title itself is a direct statement: plans are not executions. The authors are looking at how different controllers can cause an execution shift that messes up the world model's predictions during deployment.

Taro: It sounds like they’re focusing on that moment right after you leave the simulation and hit the real road where things aren't exactly as you expected.

Rosa: Right. And what they show is that we can adapt the frozen world model planner by keeping the original planned trajectory as the input but using some learned controller-specific execution evidence to modify how it imagines that future, which they call adapting the latent rollout.

Dev: The big idea here is moving away from simply substituting executed trajectories for planned ones and instead adapting what's imagined based on how well a specific controller has behaved before.

Taro: So it’s about learning the signature of a controller’s execution style and using that signature to fine-tune the world model’s prediction mechanism without ever touching the high-level plan.

Rosa: Right. It suggests that instead of trying to make the execution match what was planned, we should use execution data to correct how well the model predicts what happens next for *that specific controller*.

The paper's summary: Dev: To summarize the paper, they introduce ExecutionBridge, which has two main parts: a Controller Encoder and a Latent Bridge. The Controller Encoder learns a compact representation of the controller that captures those persistent execution characteristics from the planned and executed trajectory pairs.

Rosa: That encoder doesn't need explicit labels or dynamics parameters; it just learns this representation by optimizing an auxiliary task where some execution decoder predicts the execution of held-out query trajectories for training supervision.

Taro: So they train this encoder to recognize *how* a specific controller tends to execute things, not just what the trajectory looks like in isolation.

Dev: And then, at deployment time, for any candidate trajectory, the frozen world model produces its native latent rollout conditioned on this learned controller representation.

Rosa: Then the Latent Bridge steps in to predict a bounded correction to that native ego latent using a formula modulated by a learned gate and projected onto some trust region of radius epsilon. This correction is injected into the ego-related component of the original rollout.

Taro: So it’s like they are taking what the world model *thinks* should happen for that plan and nudging it based on what we know about this specific controller's execution tendencies.

Dev: The main takeaway here is that by keeping the original planned trajectory as the conditioning input, you get better decision quality across unseen controller configurations because you are adapting the imagined future while preserving the semantic role of the plan for downstream control.

The paper's improvements: Rosa: What they show as an improvement is that ExecutionBridge consistently improves planning performance, measured by PDMS, across ten unseen controller configurations and multiple frozen world model planners.

Dev: The results are quite strong when you look at the low-score subset; the PDMS goes up from thirty-two point zero four to forty-six point one three, which is a gain of fourteen point zero nine points on that subset alone, which is substantial compared to what they found from just substituting executed trajectories.

Taro: It seems like the adaptation mechanism works well because it’s not just tweaking the geometric error; it actually improves the ranking of candidates in a way that matters for decision making.

Rosa: And they noted something interesting about how the method scales: it remains largely insensitive to the support set size, with planning performance staying nearly unchanged when you go from sixty-four pairs up to one thousand twenty-four pairs.

Dev: That’s important because it means we don't need a massive amount of paired data from deployment controllers just to get this adaptation mechanism working reliably. It suggests that the controller representation learned by the encoder is capturing enough persistent information.

Taro: So, if we can infer those characteristics from a relatively small set of examples, it’s much more practical for real-world deployment than needing huge datasets for training.

Conclusion: Rosa: To wrap up, the paper "Plans Are Not Executions: Adapting Frozen World-Model Planners to Controller-Induced Execution Shift" suggests that we should use execution evidence not to replace the plan, but to adapt how we imagine the future for a specific controller.

Dev: The core idea is that by inferring controller-specific execution characteristics via the Controller Encoder and using them in the Latent Bridge, you can achieve better decision quality across unseen controllers while keeping the original planned trajectory as our anchor.

Taro: I just want to add that this framework isn't tied to any specific world model architecture; it just adapts the latent representation conditioned on those learned controller characteristics, which makes it quite versatile for different setups.

Rosa: It really seems like a simple principle: preserve the plan’s semantic role and use execution evidence to adapt the future imagined for it. ExecutionBridge consistently improves planning across unseen controllers and multiple frozen world model planners.

Dev: It moves the focus from geometric accuracy of execution to semantic alignment between what we planned and how a specific controller actually behaves in motion.

Taro: It’s a useful tool for when you have a fixed plan but the vehicle dynamics or control system introduces unexpected execution shifts that break the model's assumptions.

Rosa: That’s it for this paper. We'll be looking at other work next time, but this one shows how to use execution data smartly to improve planning without changing the plan itself.