- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
ForceWAM presents a framework that leverages world-model predictions to guide robot action generation in contact-rich manipulation tasks. Incorporating predicted force information provides additional physical cues for action generation, leading to substantial improvements in task success rates. The effectiveness and robustness of the framework are further demonstrated through real-world experiments. However, I find the methodological novelty relatively incremental, and the experiments do not sufficiently establish the specific advantages of the proposed architectural design. Furthermore, the experimental evaluation is limited to three task families using a self-collected dataset, raising concerns about generalization. There are also several minor presentation issues that make the technical details unnecessarily difficult to follow. Overall, I would consider increasing my score if the authors could more convincingly demonstrate that the contribution extends beyond incorporating force information into an existing world-model-based action generation framework.
Critical strengths
-
Well-motivated framework for contact-rich manipulation. The integration of force information into action generation is important for improving the physical understanding and interaction capabilities of robotic policies. Using successful task demonstrations for future prediction while incorporating task-agnostic play data into inverse dynamics learning is intuitive and practically meaningful.
-
Promising experimental performance. The experimental comparisons, while not entirely comprehensive, cover several representative baselines. ForceWAM demonstrates substantial improvements in success rates across the three evaluated task families, providing encouraging evidence of its effectiveness in contact-rich manipulation.
-
Real-world experimental validation. I particularly appreciate that all experimental evaluations are conducted on physical robots, with supplementary videos illustrating the execution process. These demonstrations provide useful evidence of the practical feasibility of ForceWAM and help readers understand how the framework operates in contact-rich scenarios.
Critical weaknesses
- Presentation and mathematical notation.
-
In Section 3.1, when introducing the observation (o_t), I suggest explicitly defining its constituent variables and their dimensions to improve mathematical clarity and rigor.
-
Line 152: It would be clearer to explicitly state the meaning of the first factor in Equation (1), rather than requiring readers to identify the corresponding component from the equation.
-
Line 241: Since the observation has already been defined mathematically, I suggest reusing the established notation for consistency and simplicity.
-
Line 242: The physical meanings of (C_t^{\mathrm{slow}}) and (C_{t,k}^{\mathrm{fast}}) are not immediately clear. I recommend introducing these variables together with their corresponding definitions and explaining what information each represents.
-
The connection between Figure 2 and Section 3.4 is not sufficiently explicit. Referring directly to the relevant components of Figure 2 when explaining the slow-fast execution mechanism would make the methodology easier to follow.
-
Line 267: I suggest explicitly defining (\mathbf{u}_{s+k}) and clarifying its relationship to the predicted action and the command sent to the robot controller.
- Limited methodological novelty.
-
My primary concern is the novelty of the proposed framework. As I understand it, ForceWAM first employs a world model to predict future observations and then uses a diffusion-based inverse dynamics model to generate actions conditioned on those predictions. Similar formulations have already been explored in previous works, such as Video Prediction Policy (ICML 2025) and Video Generators are Robot Policies (arXiv:2508.00795). Although ForceWAM additionally incorporates force information, force-aware action generation has also been investigated in recent work, such as Force Policy (arXiv:2602.22088). Therefore, I am not fully convinced that the proposed framework introduces a sufficiently substantial methodological contribution beyond combining existing world-model-based action generation with force-aware policy learning. I would appreciate a more explicit discussion and comparison to establish its novelty.
-
Another concern is the selection of baselines. The authors primarily compare against existing world-action models and several force-aware policies, but do not include certain recent methods that directly incorporate force measurements into action generation without relying on a world model, such as Force Policy. A comparison with this category of methods would help demonstrate whether the proposed combination of world prediction and force information provides advantages beyond force-conditioned action generation alone.
-
The authors also motivate their method by arguing that conventional end-to-end policies entangle the learning of task-compatible outcomes and action responses. However, actions and world evolution are inherently coupled: actions change the environment, while changes in the environment influence subsequent actions. I am therefore interested in understanding the motivation for explicitly decoupling these learning processes. In particular, how does the proposed architecture handle the temporal dependencies and potential asynchrony between world evolution and action generation during execution? A clearer explanation of why this decomposition is beneficial would strengthen the methodological contribution.
- Insufficient experimental validation and ablation studies.
-
I did not find an ablation study that directly demonstrates the advantages of separating world-model prediction from action generation. In principle, these components could be integrated into a single model that directly predicts future actions while jointly learning world dynamics. A controlled comparison between the proposed decoupled architecture and a jointly trained alternative would provide stronger evidence that the decomposition itself contributes to the reported performance improvements.
-
The experimental evaluation is relatively limited in task diversity. The authors evaluate ForceWAM on a self-collected dataset covering three task families and four conditions, without demonstrating its effectiveness on additional contact-rich manipulation benchmarks. For example, the publicly available FAWAM dataset includes other manipulation tasks, such as fruit peeling and board cleaning. Evaluating ForceWAM on such tasks, where compatible observation and control interfaces are available, would help establish whether the proposed framework generalizes beyond the specific scenarios considered in this paper.
Questions for authors
Please refer to the concerns raised in the Weaknesses section, particularly regarding the methodological distinction from existing world-model-based action generation frameworks, the motivation for decoupling world prediction and inverse dynamics learning, and the experimental evidence supporting the benefits of this architectural design.
7 comments
Response to Reviewer Qy1k (2/5)
W2.1: novelty.
Concern: Predicting the future with a world model and generating actions with a diffusion-based IDM has been explored (VPP, Video Policy), and force-aware action generation also exists (Force Policy), so the contribution beyond combining the two is unclear.
ForceWAM is more than a world-model policy with an added force input. Its contribution is a way to use play data for contact-rich manipulation, which covers the following three aspects.
- Play data matters for contact-rich manipulation. Demonstrations stay near a nominal contact trajectory (about 10 N in Slide), and play adds harder and lighter pressing, slipping and loss of contact. With demonstrations and ForceWM fixed, play raises success by 15–45 pp, and success rises with the amount of play (Table 1, Fig. 4).
- A visual-wrench future as the interface makes play usable. We treat contact execution as inverse dynamics conditioned on a visual-wrench future. An IDM conditioned on the recorded future can be supervised by any recorded interaction, so task-agnostic play trains it while ForceWM learns from demonstrations only. Mixing the same play into a policy or a joint world-action model hurts (+Play rows of Table 1; Joint-WAM in Post 5). The wrench part is needed because a visual future does not determine force. On Slide, a visual-only IDM reaches 15% and a wrench-only IDM 20%, against 85% with both (Table 2).
- A reactive IDM designed for the force signal. Contact force changes within an action chunk and cannot be read from the image, so the IDM is causal in the measured wrench: action token sees measured wrench 0:, and the reference wrench only at offsets larger than . This gives within-chunk reaction with no intervention data. Without it, success drops from 85/95/85 to 40/50/40 (App. G.1).
Table R1. Differences from VPP, Video Policy and Force Policy
| Prior work | What it provides | What differs in ForceWAM | Why it matters |
|---|---|---|---|
| VPP, Video Policy | Action module conditioned on a predicted visual future, trained on demonstrations | A visual-wrench future, and an IDM that also learns from play | Sliding at 5 N looks the same as sliding at 15 N, so a visual future leaves force open |
| Force Policy | Interaction frame, per-axis force or position control, and a reference wrench, executed by a hybrid force-position controller | A predicted visual-wrench future as the condition of the action model | It does not predict how the interaction should evolve, and it learns from demonstrations only |
The revised related work (Sec. 2) now discusses VPP and Video Policy.
Three results show that the gain does not come from the force input alone.
- A force input is not enough. The IDM with live wrench feedback and no future condition reaches 15/30/35% (Table 2), and force-reactive baselines without a world model reach at most 60% (Table 1).
- Adding force to a jointly trained WAM is not enough. On the same backbone and data, a model that jointly predicts video, wrench and actions averages 28% (Table R2, Post 5).
- Play helps through the decoupled IDM. It lowers Joint-WAM by 5 pp and raises ForceWAM by 28 pp (Table R2).
Response to Reviewer Qy1k (3/5)
W2.2: choice of force-conditioned baselines.
Concern: The baselines do not include recent methods that use force measurements directly in action generation without a world model, such as Force Policy.
The category you describe, methods that feed force measurements directly into action generation without a world model, is represented in Table 1 by RDP, ImplicitRDP and ForceVLA. Force Policy itself uses RDP and ForceVLA as baselines. We did not include Force Policy because its setting differs from ours in three respects.
- Control interface. Force Policy's outputs are executed by a hybrid force-position controller. ForceWAM, like every method in Table 1, sends TCP-pose targets to the same Cartesian impedance controller and regulates force indirectly through pose targets.
- Supervision. Force Policy needs per-segment interaction-frame and control-mode labels, obtained from demonstrations by a power-based analysis and a vision-language model. Our data has no such labels.
- Perception. Its global policy relies on 3D perception from a global RGB-D camera, and our models use a wrist RGB image.
Running Force Policy on our platform would change the controller, the labels and the perception at once, so the comparison would not isolate the effect of the predicted future. The force-conditioned baselines in Table 1 share our controller and inputs. They reach at most 60%, and ForceWAM reaches 85–95%. Force Policy is complementary to our method, and its interaction-frame action space could serve as the output space of our IDM.
W2.3: actions and world evolution are coupled, so why decouple?
Concern: Actions change the environment and the environment influences later actions. Why decouple the two learning processes, and how are temporal dependencies and asynchrony handled during execution?
We agree that they are coupled, and ForceWAM models the coupling in two places. What we decouple is the source of supervision.
- World evolution and contact are predicted jointly. ForceWM generates future video and future wrench in the same denoising pass over the same time window, so the visual and contact futures are synchronized descriptions of one interaction.
- The IDM maps this joint future to actions. outputs the actions that realize the predicted visual-wrench evolution from the current state, and it closes the loop on the measured wrench.
Inverse dynamics suits contact for a physical reason. Compliant contact can be modeled as a spring: in the quasi-static case, contact force is proportional to the offset between the target and the actual pose, (Chen et al., 2026, Eqs. 3–4). Under the Cartesian impedance controller we use, the same relation links the commanded TCP target to the contact force it produces, . The action is then determined by where the robot should be and how much force it should apply, and these are given by the visual future and the wrench future. Both futures are needed for this reason (Table 2, Slide: visual only 15%, wrench only 20%, both 85%). The mapping is set by the robot, the controller and the contact. It does not depend on the task instruction, so learning it needs no task labels.
Response to Reviewer Qy1k (1/5)
Thank you for the constructive review, and for saying clearly what would change your assessment. We respond to each point below. We have uploaded a revised PDF; changes are marked in blue and the new experiments are in App. G.
W1: presentation and notation. We revised all six points in the paper.