Two-stage VLA training with a horizon-16 latent future interface
A practical next step for VLA teams is a two-stage training pipeline with an explicit latent future target, then a short-horizon action chunk policy conditioned on that target. DIAL gives a concrete recipe: predict visual features at horizon 16 with the VLM, train the controller against ground-truth future features first, then switch to joint training so action loss can refine the perception stack without pushing it straight into low-level control. The payoff in the reported setup is large enough to justify an internal replication effort. On RoboCasa GR1 Tabletop, the paper reports state-of-the-art results with 2,400 trajectories in a regime where prior full-data runs used 24,000.
The immediate user is the robotics team that already has a VLM-backed manipulation policy but is spending heavily on demonstrations and fighting instability when it fine-tunes end to end. The concrete build is narrow: add a future-feature head, keep the latent in the same ViT space as perception, and evaluate whether the controller still benefits when the future prediction is mandatory input rather than an auxiliary loss. A cheap check is to rerun one tabletop benchmark at fixed data budgets and compare success rate and training stability between direct action prediction and the latent-future interface. If the gain holds at a few thousand demos, this changes how teams budget data collection for manipulation training.