World models are becoming planning and simulation engines

AI systems can increasingly predict future states and generate interactive environments. The useful question is not whether a rollout looks real, but whether actions, uncertainty and task outcomes transfer to the real system.

Evidence confidence93%
Hype riskHigh
Adoption stageResearch and early controlled deployment
The 60-second answer

What is happening?

A world model tries to predict how a situation will change. It might imagine what a robot will see after moving its arm, what traffic could do after a steering action or how a virtual environment will respond to a player. That can reduce some real-world trial and error and create cases that would otherwise be rare or dangerous to collect. The imagined future is still a model output. It can look convincing while moving the wrong object, ignoring friction or leaving out an unlikely outcome that matters. The safest use is to treat the prediction as one input to planning and then compare it continuously with what actually happens.

Why now

Why this trend is moving

  • 01Genie 3 can generate interactive visual environments in real time and sustain them for several minutes under limited action controls.
  • 02V-JEPA 2 and V-JEPA 2.1 use self-supervised video prediction to support physical understanding and action-conditioned robot planning.
  • 03NVIDIA Cosmos packages world foundation models for prediction, reasoning and controllable synthetic data generation.
  • 04DreamerV3 shows that latent world models can support control across diverse tasks without rendering photorealistic futures.
  • 05Driving, robotics and game systems increasingly use generated futures to train, test or rank actions before real execution.
  • 06Diagnostic benchmarks are revealing that realistic video quality does not establish action fidelity, physical consistency or policy transfer.
What it changes

What this means in practice

  • A world model should be selected for the decision and state variables it must preserve, not for visual quality alone.
  • Action-conditioned models need explicit control units, timing and paired counterfactual tests from the same starting state.
  • Stochastic environments require multiple possible futures and calibrated uncertainty rather than one confident rollout.
  • Short receding-horizon planning reduces accumulated error because new real observations repeatedly correct the model.
  • Synthetic scenarios should be tracked separately from real data and judged by improvement on held-out real conditions.
  • Physical consistency, task success and policy transfer need independent tests beyond human preference or video metrics.
  • The full model, tokenizer, planner, controller and evaluator stack should be versioned and monitored for prediction drift.
Engineering Lens

What the headline leaves out

This is the practical technical view: how the system is put together, where it can fail, and what a real deployment asks from the team running it.

01

How it is built

A production world-model system starts with a bounded decision, action space, state definition and prediction horizon. Video, sensors, maps, text and control records are synchronized with explicit units and timing. A model learns transitions in pixels, tokens, latent features or structured variables. At runtime, proposed actions generate one or more future rollouts, which are scored against goals, constraints and uncertainty. A planner selects an action, while deterministic control and safety limits remain outside the model. The real outcome is then observed and compared with the prediction. Residuals, rare failures and operating-domain changes become held-out tests before the next model version is qualified.

02

How inference behaves

World models learn transition structure from sequences. Autoregressive visual models predict the next frame or token repeatedly. Latent models compress observations and predict future representations, rewards or values. Action-conditioned models include control inputs so alternative actions create alternative futures. Planning may sample action sequences, optimize them with model-predictive control or train a policy inside imagined trajectories. Uncertainty can be represented through multiple samples, probabilistic latent states or ensembles. Every approach trades interpretability, computation, visual detail, horizon and task fidelity differently.

03

What the tests can miss

A credible evaluation separates visual realism, action fidelity, physical consistency and task fidelity. It tests matched actions from the same state, long-horizon object and spatial consistency, isolated physical concepts, uncertainty calibration, unfamiliar conditions, planner exploitation and policy transfer to real environments. Synthetic training value must be demonstrated on held-out real data or hardware. Reports should identify the representation, horizon, action schema, control rate, sampling method, planner, evaluator and real confirmation process.

04

What deployment involves

Begin with offline prediction, anomaly analysis or synthetic scenario generation. Add advisory planning only after action effects and uncertainty are calibrated. Closed-loop control should remain bounded to environments with short horizons, frequent observations, independent constraints and a safe fallback. Use generated data to complement—not replace—real and conventional simulation evidence. Promote model changes through fixed action-response regressions, held-out real tests, canaries and rollback. Monitor prediction residuals by object, action, environment and horizon after release.

05

Where the risks sit

World-model pipelines ingest large video, sensor, map and control datasets and often generate scenarios that influence physical agents. Poisoned action logs, altered calibration, mislabeled controls or manipulated maps can change predicted consequences. Protect dataset lineage, sensor configuration, model artifacts and planner policies with access controls and signed versions. Generated scenes may expose faces, locations, vehicles or proprietary facilities. Models must not convert retrieved text or generated visual content into physical authority without independent policy and controller checks.

06

What it really costs

Costs include data collection, video processing, tokenization, model training, GPU inference, scenario storage, planner sampling, human review, simulator integration and real-world confirmation. Photorealistic generation can be substantially more expensive than compact latent prediction or conventional simulation. The correct denominator is a verified improvement: a real failure found, a policy gain, a physical test avoided or a design decision improved. Generated hours and attractive rollouts are activity measures, not economic value.

07

What the evidence supports

The evidence now reaches beyond one architecture. DreamerV3 demonstrates broad model-based control through latent imagined trajectories. Genie 2 and Genie 3 generate action-controllable environments, with Genie 3 reporting real-time interaction and longer consistency under its stated limits. Meta reports that V-JEPA 2 can predict physical dynamics and support action-conditioned robot planning after limited robot post-training. NVIDIA Cosmos provides models and tooling for world prediction, reasoning and synthetic physical-AI data. Driving and game research adds further action-conditioned examples. The limits are just as important. Google lists restricted action space, imperfect real-location accuracy, multi-agent difficulty and finite interaction duration. WorldModelBench, ACT-Bench, WorldBench and recent physical-consistency studies find that strong visual generation can still violate instructions, physics and real task outcomes. Taken together, the evidence supports world models as bounded simulation and planning components—not authoritative replicas of reality.

How it works in practice

World models can help an AI system predict how an environment may change and compare possible actions before acting. That does not make a generated future true. Production value depends on action fidelity, uncertainty, state consistency, task-critical physics, coverage of rare conditions and continuous comparison with the real environment.

Architecture Constraints Benchmarks Security Deployment
The full system

How the parts work together

The headline technology is only one part of the product. Reliability, security and cost are usually decided by the handoffs around it.

  1. 01

    Decision and environment boundary

    Define the decision the model will support, the state variables that matter, the allowed action space, the prediction horizon and the consequences of a wrong forecast. A visually rich simulation is not a specification.

  2. 02

    Observation, action and outcome schema

    Normalize video, sensors, text, maps, controls, timestamps and rewards into explicit observations, actions and outcomes. Preserve coordinate frames, units, latency and missing-data indicators.

  3. 03

    Representation and dynamics learning

    Learn a predictive state in pixels, tokens, latent features or structured variables. The model must retain task-critical objects and relationships rather than only reconstructing attractive images.

  4. 04

    Counterfactual rollout

    Condition the model on a proposed action or policy and generate one or more plausible future trajectories. Stochastic environments require a distribution of outcomes, not one cinematic answer.

  5. 05

    Scoring and planning

    Evaluate predicted trajectories against goals, constraints, safety limits and uncertainty. A controller, planner or policy selects an action using the model as evidence rather than unrestricted authority.

  6. 06

    Real-system execution

    Execute through deterministic controllers and independently enforced limits. Observe the actual outcome and stop when state, timing or confidence moves outside the validated operating domain.

  7. 07

    Residual and drift analysis

    Compare predicted and observed state, action effects, contacts, timing and task outcome. Separate model error from sensor, controller and environment changes.

  8. 08

    Recalibration and governed update

    Promote real failures into held-out tests, update data or models under version control, and repeat simulation-to-reality qualification before deployment expands.

Back-of-the-envelope planning

Estimate the limits before the demo

These equations are planning tools rather than substitutes for testing. They help expose a design that is unlikely to fit its hardware, budget, reliability or risk limits.

A useful rollout must preserve the action consequence

action fidelity = P(predicted outcome matches real outcome | state, action, horizon)

A model can generate a realistic-looking future while responding incorrectly to the chosen action. Action fidelity should be measured on the variables that drive the decision, not only by visual similarity.

  • A steering command must change the predicted vehicle path in the correct direction and magnitude.
  • A robot push must preserve contact, object motion and obstruction.
  • A game action should affect the controlled character rather than an unrelated scene element.

Rollout error compounds with horizon

long-horizon reliability ≈ Π(step transition validityᵢ)

Transition errors are correlated, so this is an intuition rather than a calibrated probability. It shows why small per-step mistakes can make long imagined trajectories unreliable even when early frames look convincing.

  • A one-degree heading error can become a lane departure later in the rollout.
  • A missing object may invalidate every later robot plan.
  • Short receding-horizon planning can reduce exposure to accumulated error.

Simulation value depends on real transfer

transfer efficiency = real-world improvement attributable to simulation ÷ simulation, validation and integration cost

Generated scenarios are valuable only when they improve a real policy, test, design or decision. Count the cost of model inference, scenario review, duplicate cases, false failures and physical confirmation.

  • More synthetic driving video is not useful when action labels are wrong.
  • A rare-event simulator may justify its cost by revealing one reproducible safety weakness.
  • A compact latent model may create more value than a photorealistic model when planning accuracy is higher.
Prediction is broader than video

A world model is a decision model of change, not simply a video generator

The term world model covers several architectures. Dreamer learns compact latent dynamics and trains a policy inside imagined trajectories. V-JEPA predicts future representations without reconstructing every pixel. Genie and Cosmos generate action-conditioned visual environments. Driving models such as GAIA-1 create future scenes from video, text and vehicle actions.

These systems share one operational idea: learn enough about state transitions to ask what may happen next. Their outputs are not interchangeable. A latent state may be excellent for control but impossible for a person to inspect. A photorealistic rollout may be easy to review yet omit force, mass or geometry needed for planning.

The first design question is therefore not “Which world model is best?” It is “Which state, action effect and horizon must be predicted for this decision?”

  • Name the decision and target variables before choosing an architecture.
  • Distinguish video generation, latent prediction and structured simulation.
  • Do not use visual quality as a proxy for control accuracy.
  • Preserve access to the real observations behind generated rollouts.
Compression chooses what survives

Pixel, token and latent models lose different information

Pixel-space models preserve visible detail but are expensive and can spend capacity on texture that does not matter to the task. Discrete video tokens reduce sequence length but may remove small objects or subtle motion. Latent predictive models avoid reconstructing everything, although their internal state is harder to interpret and may still discard a critical feature.

The representation should be judged through downstream consequences. A ball that disappears for one frame may be cosmetic in a generated clip but catastrophic in a game policy. A driving model that renders a convincing street but shifts the lane boundary is unsuitable for trajectory testing.

Representation audits should identify which objects, relationships and physical quantities are retained across horizon, occlusion and revisiting. Reconstruction quality alone does not answer that question.

  • Create task-critical concept tests.
  • Measure object permanence and spatial consistency.
  • Inspect failures after compression and tokenization.
  • Use structured state alongside video when exact quantities matter.
A simulator must listen to the controller

Action conditioning is the difference between a movie and a planning environment

For planning, the model must respond correctly to the action being evaluated. ACT-Bench was created because leading driving world models could produce plausible futures while failing to follow the requested motion. Genie likewise has to infer which object a keyboard action controls.

Action semantics should be explicit: units, coordinate frame, control rate, delay and actuator limits. Training data often mixes human inputs, robot commands, inferred motion and text descriptions. Treating these as equivalent can produce a model that recognizes action labels without learning their causal effect.

Evaluate interventions, not correlations. Compare matched starting states under different actions, including actions that are rare, ineffective or unsafe. The rollout should change where the real environment changes and remain invariant where the action has no effect.

  • Document action units and timing.
  • Test paired counterfactual actions from the same state.
  • Measure magnitude and direction, not only action category.
  • Reject rollouts that respond to intent while ignoring physical control.
The future is not one frame sequence

A single plausible future can hide the outcome that matters

Many environments are partially observed and stochastic. A pedestrian may stop or cross. A grasp may hold or slip. Another agent may react in several reasonable ways. A deterministic rollout can look confident because it commits to one branch, not because the branch is well supported.

Planning systems need calibrated uncertainty or multiple trajectories. The model should expose where futures diverge, which states are outside training coverage and how sensitive the plan is to alternative outcomes. Rare but severe branches deserve more weight than their frequency alone suggests.

Sampling more videos is not enough when all samples share the same blind spot. Diversity, probability calibration and coverage of decision-relevant outcomes should be evaluated independently.

  • Generate and score multiple futures where outcomes are ambiguous.
  • Calibrate branch probabilities against observed frequencies.
  • Track epistemic uncertainty for unfamiliar states.
  • Include low-frequency high-consequence outcomes in planning.
Imagine, score, act, observe

World-model planning should stay short, constrained and closed loop

Dreamer-style agents learn policies from imagined latent trajectories, while model-predictive control evaluates candidate action sequences and executes only the first action before observing again. V-JEPA 2-AC demonstrates image-goal planning for robot manipulation after action-conditioned post-training.

Receding-horizon control limits the damage from model drift because each real observation corrects the plan. It does not eliminate error. The planner can exploit model weaknesses, choosing actions that look rewarding in imagination but fail in the real environment.

Hard limits, conservative objectives and out-of-distribution detection should sit outside the learned rollout. High-impact actions require a real-system verifier or conventional controller that can reject an attractive but invalid plan.

  • Prefer short replanning horizons when feedback is available.
  • Penalize uncertainty and boundary violations.
  • Test whether the policy exploits simulator artefacts.
  • Keep stabilization and safety controls independent of generated futures.
Generated worlds expand coverage

Synthetic scenarios are useful only when their labels and dynamics are trustworthy

Genie, Cosmos and driving world models can produce scenarios that are expensive, rare or dangerous to capture. They can vary weather, layout, object placement and agent behavior, helping teams train or stress-test policies beyond the available real dataset.

The risk is synthetic certainty. A generated scene arrives with an implied answer about geometry, motion and consequence, but those labels may reflect the model’s error. Training repeatedly on the same simulator can teach a policy its shortcuts.

Maintain a provenance boundary between real and generated data. Measure whether synthetic cases improve performance on held-out real conditions, and keep a real-world confirmation set that the generator never sees.

  • Label generated data by model, prompt, seed and action schema.
  • Deduplicate near-identical synthetic trajectories.
  • Measure transfer on held-out real data and hardware.
  • Do not allow synthetic validation to certify synthetic training.
Pretty rollouts can fail physics

World-model evaluation needs diagnostic physics and task outcomes

WorldModelBench adds instruction following and physics adherence because general video-quality metrics miss violations such as changing object size. WorldBench separates concepts such as object permanence, perspective, friction and viscosity so a strong average cannot hide a specific physical failure.

Task-level evaluation is equally important. A generated environment should preserve whether the same policy succeeds, fails or collides compared with the real environment. Recent work on physical consistency and frozen Atari world models shows that visually coherent rollouts can still misrepresent task-critical dynamics.

Report performance by horizon, action type, object, material and operating condition. Human preference scores are useful for appearance, but physical and control claims require measurements tied to the represented system.

  • Separate realism, action fidelity and task fidelity.
  • Use diagnostic tests for individual physical concepts.
  • Compare policy outcomes in model and reality.
  • Inspect long closed-loop rollouts, not only short clips.
A learned simulator becomes infrastructure

Versioning and drift matter as much as model quality

A production world model depends on video pipelines, sensor calibration, action logs, tokenizers, checkpoints, scenario generators, planners, evaluators and hardware interfaces. A change to any component can alter the predicted future without changing the product interface.

Real environments also drift. New vehicles, tools, lighting, surfaces, software and human behavior can invalidate earlier calibration. Residual monitoring should compare predicted and observed transitions and identify the operating slices where the gap is growing.

Economics should be measured against the decision improved: physical tests avoided, failures found, data collected, policy performance gained or design cycles shortened. Large-scale photorealistic generation is not automatically cheaper than focused conventional simulation or real testing.

  • Version data, tokenizer, model, planner and evaluator together.
  • Monitor real prediction residuals by operating slice.
  • Support rollback when a model update changes action effects.
  • Calculate cost per verified real-world improvement.
Test it properly

What a benchmark worth believing should report

A performance number means little unless the workload, system configuration and quality bar are fixed. This is the minimum record a team should keep.

MetricHow to measure itWhy it matters
Action fidelity Compare predicted and observed state changes for matched initial states and actions. A planning model must respond correctly to control inputs.
Task-critical concept retention Track objects, boundaries, contacts and relationships required by the downstream decision. Compression can erase small but decisive information.
Long-horizon consistency Measure spatial, identity and dynamics errors as rollout duration increases. Autoregressive errors accumulate and may appear only after revisiting a state.
Physical-law diagnostics Test isolated concepts such as permanence, collision, gravity, friction, conservation and material behavior. Average visual quality hides specific physical failures.
Counterfactual separation Run different actions from the same state and measure whether predicted outcomes diverge correctly. Correlation with observed video is not evidence of causal action understanding.
Uncertainty calibration Compare predicted branch probabilities or confidence with observed outcome frequencies. Planning needs to know when several futures remain plausible.
Out-of-domain detection Test unfamiliar objects, environments, controls and combinations withheld from training. A confident rollout outside coverage is dangerous.
Policy-transfer fidelity Compare policy success, failure and safety events in the model and the real environment. A simulator is useful when it preserves decision outcomes.
Synthetic-to-real gain Measure improvement on held-out real tests attributable to generated training or evaluation cases. Synthetic volume alone does not establish value.
Planner exploitation rate Identify actions selected because they exploit model artefacts rather than real dynamics. Optimization finds weaknesses in the simulator.
Prediction residual drift Monitor real-versus-predicted transition error over time and operating slices. The environment and system change after release.
Latency and throughput Report observation-to-rollout and rollout-to-action p50, p95 and p99. A high-quality future can arrive too late for the control loop.
Human review burden Record scenario screening, failure triage and physical confirmation time. Generated data can shift work into inspection.
Cost per verified improvement Include training, inference, storage, simulation, review, integration and real confirmation. World generation is valuable only when it improves a real decision or system.
Product choices

Four sensible deployment patterns

01

Offline representation and prediction model

Where it fits
Video understanding, forecasting and anomaly analysis without direct control authority.
What you take on
Lowest operational risk, but planning value remains indirect.
02

Synthetic scenario generator

Where it fits
Training and stress testing for robotics, driving, games or agents where real cases are scarce.
What you take on
Broadens coverage while creating a strong need for provenance and real-transfer measurement.
03

Advisory planning model

Where it fits
The model ranks candidate actions while a conventional controller or human approves execution.
What you take on
Useful compromise, with latency and disagreement handling added to the workflow.
04

Closed-loop model-based controller

Where it fits
Bounded environments with fast observation, short horizons, independent constraints and frequent replanning.
What you take on
Highest performance potential and highest sensitivity to model error, drift and exploitation.
Lessons from the edge cases

Where projects usually go wrong

01

Photorealism is mistaken for physical validity

What you see: Generated scenes look convincing while contacts, geometry or action effects are wrong.

What to do: Use diagnostic physics, action-fidelity and task-outcome tests.

02

The representation drops a critical object

What you see: Small tools, hazards, balls or lane boundaries disappear or change identity.

What to do: Add task-critical concept retention tests and structured state channels.

03

The model ignores action magnitude

What you see: Different control inputs produce nearly identical futures.

What to do: Test matched counterfactual actions with measured response curves.

04

One future is treated as certainty

What you see: The planner commits despite several plausible behaviors by other agents or the environment.

What to do: Generate calibrated alternatives and use risk-aware scoring.

05

Long rollouts drift

What you see: Objects move, vanish or reappear inconsistently after many steps.

What to do: Use shorter horizons, memory mechanisms and real observation resets.

06

The planner exploits simulator artefacts

What you see: High imagined reward produces poor or unsafe real behavior.

What to do: Adversarially test policies, constrain actions and verify on held-out reality.

07

Synthetic data confirms itself

What you see: The same generator supplies training and validation, creating circular evidence.

What to do: Maintain independent real and conventional-simulation acceptance sets.

08

Rare events are visually varied but dynamically identical

What you see: Many generated cases add appearance diversity without new failure mechanisms.

What to do: Measure scenario novelty in state, action and consequence space.

09

Sensor and controller delay are omitted

What you see: A policy succeeds in the model but fails when real latency is introduced.

What to do: Model timing, jitter and actuator response explicitly.

10

A checkpoint update silently changes dynamics

What you see: The same action produces a different predicted consequence after deployment.

What to do: Version complete stacks and run fixed action-response regressions.

11

Real-environment drift is not monitored

What you see: Prediction residuals grow after hardware, software or operating conditions change.

What to do: Monitor residuals by slice and trigger recalibration or rollback.

12

Simulation cost exceeds the saved work

What you see: Teams generate and review huge volumes without measurable real improvement.

What to do: Track cost per failure discovered or real-system gain.

Before release

A checklist you can actually use

  1. Define the decision, state variables, action space and prediction horizon.
  2. Classify the consequence of an incorrect rollout.
  3. Choose pixel, token, latent or structured representation for the decision—not visual appeal.
  4. Document observation units, coordinate frames, timestamps and missing data.
  5. Document action units, control frequency, delay and actuator limits.
  6. Preserve task-critical objects and relationships through compression.
  7. Use matched starting states to test alternative actions.
  8. Generate multiple futures when the environment is ambiguous.
  9. Calibrate uncertainty and identify out-of-domain states.
  10. Test isolated physical concepts as well as aggregate quality.
  11. Measure long-horizon spatial and identity consistency.
  12. Compare policy outcomes in the model and the real environment.
  13. Use short receding horizons where real feedback is available.
  14. Keep deterministic control and safety limits outside the model.
  15. Test whether planners exploit model weaknesses.
  16. Separate real, conventional-simulation and generated datasets.
  17. Preserve generator, prompt, seed, model and action provenance.
  18. Measure synthetic-data value on held-out real tests.
  19. Monitor prediction residuals after deployment.
  20. Version data, tokenizer, model, planner and evaluator together.
  21. Maintain action-response regression cases across updates.
  22. Support rollback when model dynamics change.
  23. Calculate complete cost per verified real-world improvement.
Plain-language definitions

Terms worth knowing

World model
A learned model that predicts how an environment or internal state may change, often conditioned on actions.
Latent dynamics
Predicted transitions in a compressed learned representation rather than directly in pixels or explicit physical variables.
Action-conditioned prediction
Forecasting a future state using both the current state and a proposed action.
Rollout
A sequence of predicted future states generated by repeatedly applying a model.
Counterfactual
A predicted outcome under an action or condition different from the observed one.
Model-based reinforcement learning
Learning or planning with an environment model instead of relying only on direct trial and error.
Receding-horizon control
Planning several steps ahead, executing one or a few actions, then replanning from new observations.
Action fidelity
How accurately a model represents the consequence of a specified action.
Task fidelity
How well a simulated environment preserves real success, failure and safety outcomes for the task.
Object permanence
Maintaining the identity and existence of an object when it is hidden or leaves the current view.
Epistemic uncertainty
Uncertainty caused by limited knowledge or insufficient training coverage.
Sim-to-real gap
The difference between behavior or outcomes in simulation and the physical environment.
Simulator exploitation
A policy using an error or shortcut in the model to gain predicted reward that does not transfer to reality.
Prediction residual
The difference between the state predicted by the model and the state later observed.
World foundation model
A large pretrained model intended to support prediction or generation across many environments and tasks.
About the author

H. Omer Aktas

H. Omer Aktas is the independent editor and publisher of WTFIsTrending.com. He applies more than 30 years of operational, surveillance, analytics and systems experience from regulated casino environments to questions of evidence, controls, implementation risk and deployment reality.

Source trail · 48 references

Primary references and technical starting points

These sources support the architecture, runtime, benchmark and security claims. Vendor capabilities can change, so the article records the distinction between established evidence, measured product behavior and editorial interpretation.

  1. 01 Google DeepMind: Genie 3deepmind.google
  2. 02 Google DeepMind: Genie 3 model page and limitationsdeepmind.google
  3. 03 Google DeepMind: Genie 2deepmind.google
  4. 04 Genie: Generative Interactive Environments paperarxiv.org
  5. 05 Google DeepMind: SIMA 2deepmind.google
  6. 06 Nature: Mastering diverse control tasks through world modelsnature.com
  7. 07 DreamerV3 project and implementationdanijar.com
  8. 08 PlaNet: Learning latent dynamics for planningarxiv.org
  9. 09 Dreamer: Reinforcement learning with imagined trajectoriesarxiv.org
  10. 10 Nature: Mastering Atari, Go, chess and shogi by planning with a learned modelnature.com
  11. 11 World Models foundational paperarxiv.org
  12. 12 Meta AI: V-JEPA 2 world model and benchmarksai.meta.com
  13. 13 Meta AI: V-JEPA 2 project pageai.meta.com
  14. 14 Meta FAIR: V-JEPA 2 repositorygithub.com
  15. 15 V-JEPA 2 paperarxiv.org
  16. 16 V-JEPA 2.1 paperarxiv.org
  17. 17 V-JEPA video representation paperarxiv.org
  18. 18 I-JEPA image representation paperarxiv.org
  19. 19 NVIDIA: Cosmos world foundation modelsblogs.nvidia.com
  20. 20 NVIDIA: Cosmos platform launchnvidianews.nvidia.com
  21. 21 NVIDIA: Cosmos prediction, control and reasoning updatenvidianews.nvidia.com
  22. 22 NVIDIA NIM documentation for Cosmos world modelsdocs.nvidia.com
  23. 23 NVIDIA Cosmos Predict repositorygithub.com
  24. 24 NVIDIA Cosmos Tokenizer repositorygithub.com
  25. 25 GAIA-1 generative world model for autonomous drivingarxiv.org
  26. 26 Wayve: Introducing GAIA-1wayve.ai
  27. 27 DIAMOND diffusion world modelarxiv.org
  28. 28 DIAMOND interactive world-model projectdiamond-wm.github.io
  29. 29 GameNGen neural game enginearxiv.org
  30. 30 WorldModelBencharxiv.org
  31. 31 WorldModelBench project and evaluation dataworldmodelbench-team.github.io
  32. 32 WorldBench diagnostic physics benchmarkarxiv.org
  33. 33 ACT-Bench action-controllable driving benchmarkarxiv.org
  34. 34 WorldPack long-horizon spatial consistencyarxiv.org
  35. 35 Reference-free physical-consistency assessmentarxiv.org
  36. 36 Closed-loop diagnostics of Atari world modelsarxiv.org
  37. 37 Google DeepMind: D4RT 4D reconstruction and trackingdeepmind.google
  38. 38 CARLA autonomous-driving simulator paperarxiv.org
  39. 39 CARLA simulator documentationcarla.readthedocs.io
  40. 40 Waymax data-driven autonomous-driving simulatorarxiv.org
  41. 41 Meta Habitat 3.0 embodied simulationarxiv.org
  42. 42 NVIDIA Isaac Sim documentationdocs.isaacsim.omniverse.nvidia.com
  43. 43 NVIDIA Omniverse Replicator synthetic-data documentationdocs.omniverse.nvidia.com
  44. 44 Nature: World models explainernature.com
  45. 45 Nature Machine Intelligence: A roadmap for AI in roboticsnature.com
  46. 46 NIST AI Risk Management Frameworknist.gov
  47. 47 NIST AI 600-1 Generative AI Profilenist.gov
  48. 48 ISO 34502 scenario-based safety evaluation frameworkiso.org