- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper presents an intuitive and practically motivated framework that combines lightweight runtime failure monitoring with on-demand recovery. Learning a progress signal from existing demonstration timestamps while reusing policy features is appealing. The extensive detection evaluation across two policy families, recovery comparisons, and real-robot demonstrations are strengths.
Critical strengths
The paper has an intuitive and practically relevant motivation. Runtime failure monitoring should be connected to recovery so that detecting a problem leads to corrective action. Reusing policy features for lightweight monitoring and activating additional computation when needed is an appealing design.
Critical weaknesses
1. The writing and organization could be improved.
The manuscript places considerable emphasis on numerical results and comparisons, while the core method and its design rationale receive less clear explanation. A more coherent presentation of the motivation, proposed mechanism, and relationship between components would make the paper easier to follow and its contribution easier to assess. For example,
-
The training objectives need a more precise mathematical specification. Section 3.2 describes as an action-prediction loss and as a mean squared error, but does not explicitly formulate these objectives.
-
Section 3.4 mixes the proposed method with the experimental comparison. Much of this section enumerates existing recovery operators and their evaluation settings, which would fit better in the experimental setup. The Methods section should focus on the proposed alarm-to-recovery controller and clearly distinguish the authors’ contributions from reused components.
2. Several consequential hyperparameter choices lack sufficient justification or sensitivity analysis.
For example, fixed-threshold PS uses a window of two policy decisions and raises an alarm when predicted progress gain falls below 0.001. The rule is defined, but the basis for choosing these values and their robustness across tasks and execution speeds remain unclear.
3. The methodological novelty of the recovery component appears limited.
The recovery operators largely build on existing methods, particularly FWM, so the contribution appears to lie primarily in progress-triggered activation and integration with the policy. In my view, this is an incremental extension of prior work on progress-aware heads [1,2].
[1] Ma et al., "CycleVLA: Proactive Self-Correcting Vision-Language-Action Models via Subtask Backtracking and Minimum Bayes Risk Decoding," arXiv.2601.02295
[2] Physical Intelligence, "π0.6 : a VLA That Learns From Experience," arXiv:2511.14759
Questions for authors
I am very interested in failure detection and recovery, and I appreciate the paper’s practical motivation. However, the manuscript requires substantial improvements in its presentation, justification of methodological choices, and demonstration of novelty, which currently fall below the ICLR bar. Due to these concerns, I am assigning a score of 1. I encourage the authors to address the weaknesses detailed above, particularly with respect to the writing and overall presentation.