Understand the cause
Locate the action, relation, or missing prerequisite that first invalidated progress—not just the unsuccessful outcome.
Physical causal understandingRecover, don’t just continue.
Learning from Feedback for Physical Failure Understanding and Correction
RESEARCH FILM
Why physical failures need causal diagnosis, how we train RynnBrain, and what changes during recovery.
Method diagrams and continuous simulator excerpts. Demonstrations use a GPT proxy with state-assisted control; quantitative results are reported separately from the manuscript.
01 / THE RESEARCH IN BRIEF
Reliable embodied execution requires more than generating a plausible plan: an embodied brain must understand physical causes of failure, adapt its guidance to the executor’s capabilities, and use interaction history to revise subsequent decisions. We introduce Embodied-Corrector, a corrective brain trained from RynnBrain-8B to connect observed outcomes with causal diagnosis and executable recovery.
We construct controlled failure–recovery branches from successful trajectories, changing one physical factor at a time. Evaluation-first SFT first teaches outcome judgment and cause analysis, then recovery planning. Noise-Aware Entropy-Gated Policy Optimization (NEPO) combines group-relative rewards with token-level guidance across generated and verified evaluation contexts. At deployment, the model produces Judge → Cause → Sub → Fine from public execution evidence and within-episode history.
The manuscript evaluates failure reasoning, planning transfer, and recovery with fixed execution backends. It reports 55.0% → 68.9% macro-average success with a fixed code backend and 1.2% → 7.3% success for a frozen π0.5 on RoboCasa365 Composite-Unseen. These simulation results connect improved diagnosis with more effective recovery while keeping the executor fixed.
02 / WHY RECOVERY MATTERS
Physical execution is constrained by the embodiment, controller, and environment. How can an embodied brain explain unexpected outcomes and use feedback to plan a recovery its current executor can realize?
Locate the action, relation, or missing prerequisite that first invalidated progress—not just the unsuccessful outcome.
Physical causal understandingTranslate a recovery into state-conditioned subtasks that the current controller or frozen VLA can actually realize.
Capability-aware planningUse prior actions, observations, and corrections as evidence for the next decision, without updating model parameters.
In-context adaptation“It failed” is not enough. On EB-ALFRED, cause-level feedback improves replanning more consistently than repeating the failed outcome.
03 / HOW WE TRAIN THE CORRECTIVE BRAIN
We train RynnBrain-8B with evaluation-first SFT and NEPO. A single inference connects execution evidence to four structured outputs, giving the same downstream planner a better basis for its next action.
Did the subtask succeed?
Which condition was violated?
What should happen next?
How can it be executed?
Illustrative summary of the paper’s orange-juice recovery case.
Branch successful trajectories at subtask boundaries, intervene on one factor, and pair failures with aligned correction targets. Keep only failures that are observable and recoverable.
Sources: RoboCasa365 and OmniBehavior. Source trajectories are split before perturbation generation to prevent shared prefixes across training and evaluation.
First learn Judge + Cause, then learn Sub + Fine conditioned on verified evaluations. NEPO combines group-relative rewards with entropy-gated on-policy distillation to reduce the training-to-deployment mismatch.
Verified evaluation labels are available during training only.
INSIDE NEPO
Training can use a verified evaluation, while deployment must rely on the model’s own assessment. NEPO turns this context difference into a token-level learning signal.
p · probability under the generated evaluation q · probability under the verified evaluation
THE CLOSED LOOP
The corrective brain reads public execution evidence and returns a structured correction. A fixed planner revises the workflow; the environment verifies the result.
Read the Harness details04 / FROM DIAGNOSIS TO EXECUTION
Evaluated at the brain level and with fixed execution backends. Explore the reported results across four complementary settings.
Unweighted mean across 4 OmniBehavior and 6 LIBERO-PRO conditions.
Table 3 · Explore results ↗RoboCasa365 Composite-Unseen, with the low-level policy frozen.
Figure 4 · Explore results ↗EB-ALFRED Base, without an explicit failure prompt or corrective Harness.
Table 2 · Explore results ↗Execution understanding and corrective planning across navigation and manipulation.
Dataset & evaluation code ↗| Model | Judge | Cause | Sub | Fine |
|---|---|---|---|---|
| GPT-5.5 | 52.8 | 39.8 | 72.7 | 39.4 |
| RoboBrain2.5-4B | 31.5 | 12.2 | 26.1 | 21.2 |
| RynnBrain-8B | 23.6 | 13.6 | 23.4 | 19.4 |
| InternVL3-8B | 48.3 | 26.2 | 21.8 | 17.7 |
| MiMo-Embodied-7B | 30.1 | 16.9 | 31.6 | 25.3 |
| VL-7B baseline | 52.5 | 23.8 | 23.2 | 19.3 |
| VL-32B baseline | 49.5 | 29.2 | 48.7 | 39.8 |
| RynnBrain-SFT | 75.9 | 53.4 | 68.6 | 66.7 |
| RynnBrain-OPD | 79.0 | 57.0 | 70.0 | 68.0 |
| RynnBrain-GRPO | 74.2 | 51.5 | 73.0 | 69.2 |
| RynnBrain-NEPO (ours) | 79.6 | 58.2 | 72.6 | 71.6 |
| w/o Entropy Gate | 73.1 | 50.8 | 69.9 | 68.5 |
| Model | Judge | Cause | Sub | Fine |
|---|---|---|---|---|
| GPT-5.5 | 57.7 | 43.2 | 65.4 | 41.1 |
| RoboBrain2.5-4B | 33.5 | 12.3 | 29.7 | 24.1 |
| RynnBrain-8B | 31.9 | 18.7 | 31.6 | 25.8 |
| InternVL3-8B | 40.1 | 17.9 | 32.1 | 26.8 |
| MiMo-Embodied-7B | 22.2 | 19.3 | 35.6 | 27.6 |
| VL-7B baseline | 33.7 | 13.5 | 28.8 | 26.0 |
| VL-32B baseline | 54.6 | 33.2 | 42.9 | 34.3 |
| RynnBrain-SFT | 80.7 | 51.4 | 62.5 | 61.6 |
| RynnBrain-OPD | 80.0 | 54.0 | 65.4 | 61.0 |
| RynnBrain-GRPO | 76.3 | 49.6 | 63.6 | 62.1 |
| RynnBrain-NEPO (ours) | 81.2 | 54.6 | 64.9 | 63.7 |
| w/o Entropy Gate | 75.0 | 48.7 | 63.1 | 61.4 |
Manuscript Table 1. Judge: execution outcome · Cause: failure diagnosis · Sub: next subtask · Fine: grounded action details. All values are reported in the manuscript.
POST-TRAINING DYNAMICS
Under matched VQA post-training conditions, NEPO achieves the highest answer-level reward while avoiding the low-entropy regime of vanilla OPD.
FAILURE → DIAGNOSIS → RECOVERY
6 different LIBERO-PRO tasks and 6 different RoboCasa365 tasks. Each RoboCasa task combines navigation and manipulation. Watch the visible error, the English Judge → Cause → Sub → Fine explanation, and the successful correction.
05 / CITATION
If this work supports your research, please cite the arXiv paper.
@misc{pan2026recover,
title = {Recover, Don't Just Continue: Learning from Feedback for Physical Failure Understanding and Correction},
author = {Pan, Miao and Yao, Kaixiang and Zhou, Xiaohe and Wang, Xu and Li, Qinfeng and Zhang, Wenqi and Zhang, Xuhong},
year = {2026},
eprint = {2611.15651},
archivePrefix = {arXiv},
primaryClass = {cs.RO},
url = {https://arxiv.org/abs/2611.15651}
}This entry cites the arXiv paper at arXiv:2611.15651.