- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper presents CERES, a fast–slow controller for multimodal underwater navigation that selectively augments a frozen reactive policy with corrective experts. Its central contributions are a cost-aware router, trained using matched short-horizon continuations and informed by realized-outcome memory, and an intervention framework that assigns experts distinct write targets and execution times: the State Refiner repairs the current representation, the Safety Verifier projects the current action onto a learned feasible set, and the Capability Planner revises subsequent decision context. An admissibility contract constrains expert selection and execution. Evaluation comprises 72 paired trials across three simulated underwater scenes, supplemented by router comparisons, expert ablations, targeted mechanism studies, adapted VLA baselines, and latency measurements. CERES achieves 86.1% success, compared with 66.7% for the reactive policy and 72.2% for always-on correction, while reducing normalized expert-forward load by 39.5% relative to always-on correction. The results provide evidence for selective correction, with the strongest mechanism-specific gains coming from representation repair.
Critical strengths
-
a useful formulation of selective correction
CERES distinguishes interventions by both their modification target and their time of effect, separating representation repair, current-action correction, and subsequent-context revision. This makes the allocation problem more concrete than simply deciding whether to invoke additional computation and provides an interpretable structure for studying heterogeneous controller failures. -
meaningful system-level improvements with paired evaluation
Across 72 paired trials, CERES improves success from 48/72 for System 1 and 52/72 for always-on correction to 62/72, preserving all 48 routine-task successes. Representation repair also produces a substantial targeted improvement, from 0/16 to 14/16 successes. These results support the practical value of selective correction in the evaluated simulation setting.
Critical weaknesses
-
The evaluation does not capture the closed-loop consequences of corrective computation latency.
Simulation pauses during policy inference, whereas expert decisions average 203.81 ms and reach 470.10 ms at P99 against a 50 ms simulation increment. Expert intervention is frequent, with an episode-averaged duty of 64.4%. Consequently, the reported success and safety results exclude motion and observation staleness during deliberation. Fast-path latency below 50 ms therefore does not establish responsiveness of the complete deployed controller. -
The evidence insufficiently isolates the central routing and intervention-design contributions.
With the same corrective stack, risk rules match CERES at 62/72 successes and achieve numerically higher progress and SPL. CERES reduces calls per decision by 29.6%, but total expert forwards by only 6.3%; neither metric directly establishes end-to-end computational savings. Fixed-threshold comparisons also leave the performance–cost trade-off incompletely characterized. Evidence for planning and expert composition is limited: adding CP improves targeted success from 5/16 to 6/16, while adding SV to SR reduces state-and-safety success from 87.5% to 50.0%.
Questions for authors
Four parts of questions are as follows, looking forward to receiving your rebuttals:
-
During the 200–470 ms expert computation period, what action would the deployed controller execute? Is there existing evaluation in which physics continues during inference or measured inference delays are explicitly injected?
-
How were the rule-based and uncertainty-routing thresholds selected? Are end-to-end computation measurements available for these controls and CERES, including routing, memory retrieval, diagnostic forwards, and System 1 recomputation?
-
What explains the substantial deterioration when SV is added to SR on the state-and-safety tasks? Do existing trajectory analyses distinguish conservative safety intervention from expert incompatibility or coordination failure?
-
How are SV constraint targets, CP revision/subgoal targets, and matched continuation labels generated? Please specify the continuation horizon, subsequent control policy, and whether labels are refreshed as the experts change during coordinated optimization.
2 comments
Reviewer 1hQ1 please respond to author comments
Reviewer 1hQ1 please respond to author comments
Response to Reviewer 1hQ1: Closed-Loop Latency, Routing Isolation, and Training Protocol
Thank you for recognizing the selective-correction formulation and paired evidence. We answer the four questions with additional trace analyses and post-submission diagnostics.
1. Closed-loop latency. In the submitted evaluation, simulation time pauses during inference; hence no physical command is executed during the reported 200--470 ms. We agree that P99 < 50 ms describes the complete fast path, not expert decisions.
We additionally injected the measured CUDA-synchronized delays while physics advanced at 20 Hz. A conservative 72-trial test that holds for every missed deadline remained collision-free (0/72 collisions), but achieved 48/72 successes, showing that holding alone is overly conservative. We therefore tested an event-driven policy: while correction is pending, the latest completed correction is executed only after revalidation against the fresh observation; otherwise the controller holds. Results are timestamped, stale corrections are rejected, and CP remains next-decision-only. On a post-submission diagnostic panel of 10 challenging trials, this policy achieved 10/10 successes and 0 collisions while rejecting 148 stale commits. We will identify this as a diagnostic panel, not a replacement for the registered 72 trials.
2. Thresholds, computation, and routing isolation. The uncertainty threshold (0.5) and risk thresholds (0.5/0.75) were frozen before the 72 outcomes and were not selected on Paper72. Uncertainty routing selects M0 below 0.5 and M5 otherwise. Risk routing uses uncertainty, cross-modal conflict, anomaly, and failure evidence to select a legal typed configuration under the same contract.
CERES timing is observation-ready to final action with CUDA synchronization; it includes diagnostics, routing, memory retrieval, System-1 computation/recomputation, selected experts, and aggregation. Alternative-router traces were not collected under the same fixed-load timing benchmark, so we use completed expert forwards rather than present their wall-clock times as directly comparable.
We also ran three causal temporal-randomization controls that do not inherit CERES's realized per-trial configuration multiset. They obtained 60/72, 61/72, and 61/72 successes using 40,549, 38,221, and 38,852 forwards, versus CERES's 62/72 with 31,619. CERES therefore used 17.3--22.0% fewer forwards while preserving or improving success. Together with the risk-rule result (both 62/72; 33,739 versus 31,619 forwards), this supports more efficient intervention allocation at matched success. System-level capability improvement is established separately by the paired System-1 and always-on controls.
3. SR+SV deterioration. Trace attribution distinguishes conservative intervention from expert incompatibility. On state-and-safety trials, SR achieves 14/16 and SR+SV 8/16. All six discordant losses are timeouts, not collisions. SR+SV produces 6,377 safe holds, of which 6,356 result from an empty predicted SV feasible set. Thus the mechanism is conservative empty-set handling under combined difficulty, rather than destructive overrides or CP same-decision feedback. This also explains why configuration selection matters: on action-risk trials, SV improves success from 0/16 to 7/16 and removes five collision episodes, but it should not be invoked indiscriminately after representation repair.
4. Targets and continuation protocol. SV targets are generated from the same causal snapshot and candidate action: current safety, next-step veto, risks at horizons {1,5,10,20}, the linear feasible set from the geometric/kinematic certificate, and the exact projected action. CP separately supervises a causal revision event, a graph-legal successor, and a valid local subgoal in the observed body frame; a proposal at t first affects context at t+1.
Router labels use 20-step matched continuations for the fast path and every legal configuration. Each branch starts from the identical simulator/controller state, history, RNG state, and disturbance schedule; its configuration is fixed throughout the continuation, with fresh causal observations regenerated each step. Labels are frozen before the 12-epoch coordinated stage and are not regenerated as parameters update, avoiding a moving target. SV and CP continue receiving their fixed geometric and graph-structured targets during the low-learning-rate updates.
We will incorporate these clarifications, attribution results, and appropriately scoped latency diagnostics in the revision.