From World Action Models to Embodied Brains: A Roadmap for Open-World Physical Intelligence

1. Paper overview

In one sentence: The roadmap proposes reusable physical reasoning through explicit consequence, intent and execution contracts, while leaving transfer benefits and the final model architecture to empirical testing. e-contracte-ownershipe-agendae-conclusion

Core contributions

• Source description

  The survey separates system responsibility from the representation crossing the prediction-to-control interface. Explicit images, geometry or plans, predictive latent features, and latent transition/action codes are overlapping interface families. Their abstraction level does not establish whether the complete system is modular or jointly trained. e-role-taxonomye-control-interfaces

• Source description

  The proposed WAM contract requires a decision-relevant consequence with horizon, reference frame, uncertainty and validity conditions. The embodied-brain target additionally integrates context and selects intent. Neither RGB generation nor an action vector alone defines that predictive contract. e-contract

• Source description

  Embodiment, Task and Trace Cards link local hardware constraints to goals and decision histories. Layered evaluation and admission gates are intended to make these histories useful for learning and diagnosis across systems while retaining original artifacts and embodiment details. e-cardse-learninge-evaluation-layers

↗ Enlarge figure

How to read it. Start with the upper panel: physical context and a candidate intervention enter the WAM prototype, which exposes a consequence together with horizon, frame, uncertainty and validity conditions. Then follow the lower panel's solid blue route. Context enters the embodied brain; its intent reaches the harness, which calls tools and controllers. The observed outcome returns through the Trace Card to evaluation and admission. The lower green dashed arrows carry admitted experience back to the brain and harness. The gray link identifies a predictive capability under study, rather than specifying a mandatory separately deployed WAM. Read these roles together with Table 6 and Section 4.2. e-stack-figuree-contracte-ownershipe-conclusion

What it supports. The useful unit of reuse is an interpretable interface: what is predicted, what is intended and what was executed must remain distinguishable. This separation would let an evaluator attribute an outcome to model reasoning, translation or execution, but the diagram describes the proposed stack rather than demonstrating that attribution experimentally.

Where the evidence stops. The upper WAM-to-consequence arrow is green dashed, although the legend labels that style learning feedback. The caption and Section 4.2 describe a prediction output. This unresolved style inconsistency is retained; it should not be read as an extra training step.

2. Motivation

2.1 The problem and the proposed response

2.2 What this reading follows

A robot can choose a useful motion without exposing what it expects that motion to change. This survey asks how such expectations could become reusable across controllers, bodies and tasks. Its answer links a predictive WAM interface to an embodied-brain intent interface, a physical harness and replayable experience records. The important distinction is between estimating a consequence, requesting a change and actually realizing that change. Read the diagrams as proposed responsibilities and the tables as a map of evidence requirements. They outline experiments worth building; they do not report a trained embodied brain or demonstrate that standardized interfaces already deliver general physical intelligence. e-contracte-ownershipe-agendae-conclusion

3. Research context

We place the paper in the collection through its world–action interface. The catalog labels and the reading’s assessment are shown separately.

This table preserves the labels recorded at reading time. The current major category is Related resources. View the current classification.

3.1 Evidence-based assessment

Supports the recorded classification

This is the collection’s architectural analysis, not a new related-work survey. Benchmark comparisons and their protocols appear in Section 6.

4. Problem formulation

4.1 Inputs and outputs

5. Method in detail

5.1 Ask what a prediction changes in the decision

Reader analysis

The paper's central distinction begins before execution. A WAM query couples the current physical context to a candidate intervention and returns a consequence with declared horizon, frame, uncertainty and validity. A brain then compares interventions and communicates the change it wants realized. These are different interfaces even if one network implements both. The survey's UniPi, VPP and LAPA examples show why representation alone cannot settle the question: explicit visual transitions, predictive features and latent action codes reach control through different mappings. Reader interpretation: the discriminating test is whether changing the consequence information changes intervention selection or verification under controlled execution conditions. Photorealistic video or accurate action imitation can be useful, but neither alone demonstrates that a consequence estimate supported the decision. e-contracte-control-interfacese-evaluation-boundarye-agenda

↗ Enlarge figure

How to read it. Read the upper row as responsibilities, not a timeline. An action model emphasizes commands, a VLA emphasizes semantic action generation, a WAM emphasizes intervention consequences, and the brain target compares interventions and forms intent. The lower row asks what predictive information reaches control: an explicit forecast, predictive features or a compact transition/action representation. To make the distinction concrete, Table 1 describes UniPi translating visual transitions through inverse dynamics, VPP conditioning inverse dynamics on predictive features, and LAPA grounding latent codes with robot-action labels. Those mechanisms can occupy different interface categories without dictating whether their complete architectures share parameters. e-role-taxonomye-control-interfacese-contracte-ownership

What it supports. A latent action is not automatically an executable robot command, and a future image is not automatically a control policy. The taxonomy directs attention to the mapping from a predictive representation into a controller. It also explains why this survey itself cannot be assigned a single joint-model or inverse-dynamics quadrant.

Where the evidence stops. These categories overlap. The graphic's compact labels are not exhaustive definitions: its world-model box says future image, while the text permits broader representations. Table 1 also qualifies pi 0.7's placement by its optional visual subgoals, not its overall architecture.

5.2 Carry a peg-driving intention through the harness

Reader analysis

Figure 16 gives a concrete conceptual example: drive a peg. The harness decomposes that request into acquiring a hammer, aligning hammer and peg, and executing a constrained impact. Arm motion drives the gripper, the gripper holds the external implement, and the implement acts on the peg and fixture. Figure 14 supplies the missing operational responsibilities around that chain: entity/frame alignment, capability resolution, precondition checks, synchronization and monitoring. The capability contract must expose frames, limits and failure modes so the intended effect remains interpretable at each boundary. This is the source's illustration, not a reported robot trial. Reader interpretation: replacing a controller while preserving the intent is a stronger test of reusable reasoning than success with one permanently fixed controller, especially if adapter effort and residual loss are recorded. e-pege-harnesse-harness-figuree-agenda

↗ Enlarge figure

How to read it. Follow the upper path from left to right. Intent must first be grounded, then aligned to entities and frames, resolved against a capability registry, checked against preconditions and synchronized with controllers. Runtime memory and the registry support different responsibilities beneath that path. On the right, tools and the environment produce outcomes that return to monitoring and recovery. The blue curve then leads to the Trace Card recorder. The green dashed return is labeled as admitted traces improving adapters and routing; it is a learning path, not the immediate control response. Section 4.3 supplies the capability-contract fields that make these boxes operationally interpretable. e-harnesse-harness-figuree-learninge-agenda

What it supports. The proposed harness is more than a tool-call dispatcher: it carries spatial, temporal and embodiment assumptions across the model-to-controller boundary. A useful test therefore measures whether substitutions preserve intent and expose failures, alongside task success. The paper also asks verifiers to reject infeasible requests without excessive false vetoes.

Where the evidence stops. The recorder-to-grounding shortcut does not display a separate admission box. Its label and Section 4.5 require evaluation before experience returns to learning. No adapter implementation, verifier threshold or measured benefit from this harness is supplied.

5.3 Turn a failed interaction into a targeted learning signal

Reader analysis

A failed task does not identify the component that should be updated. The paper notes that valid intent can accompany controller failure, while invalid intent may appear successful in a forgiving task. Embodiment and Task Cards establish the operating conditions; a Trace Card preserves the request, translations, selected capabilities, predictions, verifier states and observed outcome. Table 8 then separates possible learning uses instead of prescribing one universal loss: predictive reasoning, interface alignment, verifier learning and control adaptation have different signals and gates. Table 9 supplies corresponding diagnostics. Reader interpretation: learning admission should depend on whether a trace supports the intended update, not merely whether its final label is success. This motivates keeping provenance, corrections and quality flags and testing regression before promoting an update; the source leaves the implementation and thresholds open. e-feedback-limitse-cardse-learninge-evaluation-layerse-agenda

↗ Enlarge figure

How to read it. Begin with the Embodiment Card: frame conventions, calibration, control rates and limits define how to interpret an action. Move to the Task Card for the allowed observations, tools, success criteria and meaningful failure labels. Then read the longer Trace Card row as a chain linking model requests to their realization. It includes representation schema and frame, candidate interventions, selected tools, adapters, predictions, verifier outputs, controller states and outcomes. A success label alone discards most of that chain. The scaling-role column describes intended uses of the records, while Section 4.4 stresses that existing raw artifacts and storage formats can be retained. e-cardse-feedback-limitse-learninge-evaluation-layers

What it supports. A reusable training example needs the context that gives its outcome meaning. These proposed records would help distinguish a bad intention from a correct intention mistranslated by an adapter or unsuccessfully executed by a controller. That distinction is central to choosing which component should receive a learning signal.

Where the evidence stops. The table gives semantic minimum fields, not a versioned executable serialization or proof of deterministic replay. Real interactions remain partially observed, and the paper provides no measured trace-completeness threshold or demonstrated cross-dataset replay result.

5.4 Training and inference

During training

During inference

5.5 Implementation flow

1. Predict consequences before committing to an intervention

   The proposed predictive interface can expose future observations, geometric state, latent transitions, contact changes, affordances or task progress. Its value must be established by improved intervention comparison or verification. For context, Table 1 describes UniPi coupling visual trajectories to inverse dynamics, VPP conditioning inverse dynamics on predictive features, and LAPA grounding latent transition codes with robot-action labels. These are survey summaries of distinct methods, not components of a new implementation. e-contracte-control-interfaces

2. Express intent with inspectable semantics

   The brain chooses an intended physical change and communicates entities, frames, constraints, uncertainty and relevant completion or recovery conditions. The encoding may be language, code, structured geometry, learned tokens or a hybrid. A WAM can contribute predictive capability without remaining a mandatory separate module. Functional separation permits joint training when intermediate transformations remain observable. e-contracte-ownership

3. Ground and execute through capabilities

   The harness aligns entities and frames, resolves capabilities, checks preconditions, synchronizes controllers, monitors outcomes and handles recovery. A capability contract declares inputs, coordinates, preconditions, controllable variables, outputs, timing and failures. A tool is a capability endpoint; a tool model supplies specialized inference or control. The paper's peg-driving illustration decomposes intent into acquiring a hammer, aligning it with the peg and executing a constrained impact; it reports no execution trial. e-harnesse-harness-figuree-peg

4. Preserve the decision context for reuse

   The Embodiment Card records morphology, sensors, calibration, frames, rates, limits and controller assumptions. The Task Card records goals, allowed observations/tools, constraints and failure labels. The Trace Card links observations and requests to candidate interventions, representation versions, adapters, tool chains, verifier/controller states, outcomes and corrections. These are semantic requirements that can accompany existing storage formats, not a released universal schema. e-cards

6. Experiments & results

This survey proposes explicit contracts linking physical prediction, model intent, execution and reusable experience. A World Action Model estimates intervention consequences; an embodied brain forms an intended change; a physical harness translates and verifies execution. The contribution is a research roadmap with testable responsibilities, rather than a trained embodied-brain system or demonstrated performance gain. Its promised reuse remains a hypothesis (e-contract, e-ownership, e-conclusion).

6.1 Read the original evidence

↗ Enlarge figure

How to read it. Read each row horizontally before comparing its size with another resource. The supervision column tells you whether observations include target-robot commands. The scope column counts different units, such as clips, hours, trajectories or tasks. The use column records the survey's account of how a resource supports prediction, grounding or evaluation. Something-Something V2 has semantic labels but no robot commands; DROID provides synchronized real-robot observations and actions. SIMPLER is explicitly separated as an evaluation framework. Finally, check availability: the autonomous-interaction row leaves scale unspecified and does not claim a standalone public dataset. Neither missing entry should be filled from another release. e-data-scalee-data-rolese-evaluation-boundary

What it supports. The survey reports 220,847 Something-Something V2 clips and DROID's 76,000 trajectories, 350 hours, 564 scenes and 86 tasks. These quantities illustrate diversity in supervision and scope. They do not measure the performance of the proposed roadmap, and more video does not itself resolve embodiment-specific action grounding.

Where the evidence stops. This is a quantitative resource inventory, not an experimental results table. Counts and availability are the survey's reports of cited sources; those external artifacts were not independently inspected. Different units, licenses, schemas and action spaces prevent pooling the rows into one comparable total.

6.2 Results and evaluation conditions

No quantitative results are included in this reading.

6.3 Ablations and diagnostic examples

Read component removals and qualitative examples within their stated evaluation conditions.

↗ Enlarge figure

How to read it. Read the Status column before interpreting the measurements. Policy and control is marked Existing. Predictive reasoning and verification/safety are marked Both, mixing measurements used in cited literature with proposed extensions. Brain–harness grounding, tool orchestration, harness/traceability and self-improvement are Proposed. Each row then asks a different question: whether prediction captures relevant change, intent survives grounding, control succeeds, tools compose correctly, hazards are rejected, failures are attributable or updates retain safety. The table's caption defines these statuses; they describe where measurement ideas come from, not which tests this paper performed. Table 8 complements this view by associating learning objectives with required gates. e-evaluation-layerse-learninge-evaluation-boundarye-agenda

What it supports. End-task success cannot reveal which responsibility improved. The proposed diagnostics create places to look: frame consistency for grounding, false vetoes and missed hazards for verification, and regression or rollback triggers for learning. This is a useful design for future ablations, but the table contains no ablation effect sizes or new success rates.

Where the evidence stops. Existing means used in cited work, not reproduced here; Both does not mean every listed metric is established. The source gives measurement categories without a complete common protocol, numerical acceptance thresholds or evidence that a single aggregate score would be valid.

7. Analysis & limitations

7.1 What the evidence leaves open

7.2 Questions for discussion

1. Which consequence variables change intervention selection after controller quality and compute are controlled? (e-agenda)
2. How much adaptation remains local when the same intent must work with a substituted controller or tool? (e-agenda)
3. Which trace omissions prevent distinguishing an incorrect intent from a grounding or control failure? (e-cards, e-evaluation-layers)

8. Reproducibility audit

8.1 Requirements and known gaps

8.2 Proposed reproduction checks

The following checks are proposals motivated by the paper. They have not been run as part of this reading.

8.3 Reading coverage

8.4 Traceable evidence

8.5 Primary sources