Evaluation framework · Published 2026-07-10
How do you evaluate a world model? 如何判断一个世界模型真的有效?
A model is not useful merely because its video looks plausible. Evaluation must begin with the route, the decision it supports and the evidence available outside the demo. 画面看起来可信,并不等于模型真正有用。评估必须从技术路线、它要支持的决策,以及演示之外能够核验的证据开始。
Short answer / 一句话结论
First ask what the model predicts and who acts on the prediction. Then test nine checks across three layers: capability (state, control, action consequence, long horizon and fidelity), task utility (closed loop, downstream transfer and calibration), and evidence quality (reproducibility and access). Weight the checks by route. A video generator, a latent planning model and a driving simulator should not share one leaderboard or an additive total score.
先问模型预测什么、谁会根据预测采取行动,再按三层检查九项:能力层包含状态、控制、行动后果、长期一致性和保真度; 任务效用层包含闭环、下游迁移和校准;证据质量层检查可复核性与访问。权重必须随路线变化,不能相加成统一总分。
The evaluation matrix / 评估矩阵
Start at the decision, not the demo. / 从要支持的决策开始,而不是从演示开始。
- 01 · ScopeRoute / 路线What is predicted, represented or generated?
- 02 · CapabilityModel / 模型What state and dynamics does it preserve?
- 03 · UtilityTask / 任务Does it improve the downstream decision?
- 04 · EvidenceAccess / 证据Can outsiders inspect or reproduce the result?
- 05 · DecideDecision / 判断Is it useful under stated limits and missing evidence?
Evaluation framework
1. Define the route before choosing a metric
“World model” covers systems with different outputs: pixels, 3D scenes, latent states, future sensor observations or representations used by a controller. The 2018 World Models project evaluated a compact learned dynamics model through agent behavior. Genie 3 emphasizes navigable generated environments, V-JEPA 2 predictive representations, and GAIA-2 action-conditioned driving futures. The same metric cannot express success across all four.
2. Audit three layers across nine checks
Capability / What the model can preserve and predict
| Check | Question to test | Useful evidence | Common false positive |
|---|---|---|---|
| State | Does the representation preserve objects, relations and variables the task needs? | State probes, object tracking, geometry or task-state recovery. | Visually plausible frames with hidden state loss. |
| Control | Can prompts, actions or conditions change the intended variable without uncontrolled changes? | Intervention tests, controllability and disentanglement. | A prompt appears to work on selected examples. |
| Action consequence | Does the future respond correctly to the agent's action? | Action-conditioned prediction, inverse dynamics and counterfactual checks. | Passive continuation mistaken for interaction — or a model that does respond, and still shows the task succeeding when the action should have made it fail. |
| Long horizon | Do identity, geometry, goals and causal effects survive repeated rollout? | Error curves by horizon, re-entry tests and multi-step task completion. | A short clip hides compounding drift. |
| Fidelity | Are dynamics and frequencies faithful, not merely images realistic? | Physical constraints, distributional calibration and measured-world comparison. | High perceptual quality treated as physics. |
Task utility / What changes for a downstream user
| Check | Question to test | Useful evidence | Common false positive |
|---|---|---|---|
| Closed loop | Can a policy act, receive the changed state and act again? | Policy-in-the-loop evaluation and adversarial interventions. | Open-loop replay called a simulator. |
| Downstream transfer | Does the model improve planning, control, learning or data efficiency? | Task success, regret, sample efficiency and robust transfer. | A representation benchmark with no decision benefit. |
| Calibration | Does uncertainty rise when the model is wrong or outside its data? | Reliability curves, OOD detection and risk-coverage tests. | Confident output with unknown failure probability. |
Evidence quality / What outsiders can verify
| Check | Question to test | Useful evidence | Common false positive |
|---|---|---|---|
| Reproducibility and access | Can outsiders inspect the setup, data split, metric and failure cases? | Open protocol, code/model access, repeated runs and independent tests. | A company-selected demo with no test protocol. |
Do not add these checks into one score. Capability, task utility and evidence quality answer different questions. A strong result in one layer cannot compensate for missing evidence in another.
Two of these checks can also pull against each other, which is different from saying they do not substitute for each other. MiraBench, a robotic-manipulation benchmark posted in May 2026, perturbs an action so that the task must fail — too little grip force, an early release, a slipped carry — and then asks whether the predicted video still shows the task succeeding. On its reported figures, post-training one model for task success raised its completion score from 14.0 to 92.0 while its failure-preservation score fell from 48.7 to 23.1. Two boundaries belong with that pair of numbers. The post-trained model is the benchmark authors' own fine-tune of a third-party base, so it evidences that recipe rather than success-oriented post-training in general; and at the larger 14B scale the same comparison moves not at all, both models sitting at 12.8. The underlying failure — a model reproducing the outcome its training data made common rather than the one the input specified — is the same mechanism this site has already described for driving simulators as distribution bias. What is new is that it is being measured on the action-outcome axis rather than described.
There is also a check the nine above do not contain: all of them ask about the model, and none asks about the instrument that produced the score. MiraBench is worth reading on this because it publishes enough to be checked. Its optimism-bias level is scored by one vision-language model used zero-shot, and its appendix states that two different prompts were used — a standard one for action-conditioned models and a deliberately lenient one for text-conditioned models, whose rendering style differs. In the table validating that judge against human annotators, the single model scored with the lenient prompt is also the one where agreement collapses: it recovers 33.3% of the cases humans marked as biased, against 78.3% to 100% for every model scored with the standard prompt. Reported agreement overall is 87.8%. None of this is concealed — the prompts, the per-model agreement and the full configuration are printed — and an under-detecting judge inflates a reliability score rather than deflating it. A position paper from a separate group makes the general point without reference to this benchmark: model-as-judge evaluation is useful and scalable, but a judge can reward a plausible-looking outcome while missing the action-relevant error, so it should not stand as ground truth for decision usefulness. When a score comes from a judge, ask what validated the judge, on which models, and whether it was applied the same way to all of them.
3. Weight the matrix by route
| Route | Highest-weight checks | Useful metrics | Evidence boundary |
|---|---|---|---|
| Video or world generation | State, control, long horizon, physical fidelity. | Object persistence, geometry, intervention success and drift by duration. | Perceptual scores alone do not prove interaction or planning utility. |
| Interactive generated world | Control, action consequence, closed loop, long horizon. | Input latency, action responsiveness, state consistency and policy success. | A navigable demo does not establish stable agent training. |
| Predictive representation | State, downstream transfer, calibration. | Probe quality, task transfer, data efficiency and OOD behavior. | Strong representation transfer is not full scene simulation. |
| Robotics or driving | Action consequence, closed loop, fidelity, calibration, transfer. | Trajectory error, intervention validity, policy regret, rare-case coverage and real-system transfer. | Simulation results remain one layer of a deployment case. |
4. Separate three evidence layers
Developer evidence
Official releases and technical reports establish what was tested, under the developer's protocol. They are primary evidence for the claim, not independent confirmation.
Independent validation
External reproduction, downstream use and reality-linked tests establish whether results survive outside the originating team.
Editorial judgment
Synthesis can compare routes and identify missing evidence, but it must not upgrade an official claim into an industry fact.
This article is layer C. It synthesizes public primary and technical sources already reviewed by World Model Atlas. It does not introduce a universal benchmark, and it does not claim independent reproduction of the named systems.
5. Use the checklist before accepting “world model” performance
- What exactly is predicted: pixels, state, geometry, reward, action or a representation?
- What is the operational task, and which failure would matter?
- Is the test open loop or policy in the loop?
- How does error change with rollout horizon?
- Are actions interventions or only labels correlated with the future?
- Is fidelity measured against reality, or only against human preference?
- Does the model improve a downstream decision over a credible baseline?
- Are uncertainty and out-of-distribution behavior reported?
- Can an independent team inspect or reproduce the result?
- Which conclusion remains unsupported after all reported metrics?
Editorial conclusion
A credible world model is not the model with the highest single visual score. It is the model whose representation and dynamics remain useful under the interventions, horizons and downstream decisions its route requires, with uncertainty and access limits stated. Until those pieces are visible, “world model” is a research direction or product framing, not a validated capability class.
评估框架
1. 先确定路线,再选择指标
“世界模型”覆盖的系统可能输出像素、3D 场景、潜状态、未来传感器观测,或供控制器使用的表征。 2018 年的 World Models 通过智能体行为检验紧凑的学习型动态模型; Genie 3 强调可导航的生成环境,V-JEPA 2 强调预测表征,GAIA-2 强调动作条件下的驾驶未来。四者不能用同一个指标定义成功。
2. 按三层核查九项
能力层 / 模型能够保留和预测什么
| 检查项 | 要检验的问题 | 有用证据 | 常见误判 |
|---|---|---|---|
| 状态 | 表征是否保留任务需要的物体、关系和变量? | 状态探针、物体追踪、几何或任务状态恢复。 | 画面可信,但关键隐藏状态已经丢失。 |
| 控制 | 提示、动作或条件能否只改变目标变量? | 干预测试、可控性和解耦测试。 | 少量精选样例看似听从提示。 |
| 行动后果 | 未来是否会正确响应智能体动作? | 动作条件预测、逆动力学和反事实检查。 | 把被动续写误当成交互;或者模型确实响应了动作,却仍然把本该失败的任务演成成功。 |
| 长期一致性 | 身份、几何、目标和因果效果能否经受重复 rollout? | 随时长变化的误差曲线、重返测试、多步任务完成率。 | 短片掩盖了逐步累积的漂移。 |
| 保真度 | 动力学和事件频率是否忠于现实,而不只是画面逼真? | 物理约束、分布校准和真实测量对照。 | 把感知质量当成物理正确。 |
任务效用层 / 下游用户获得了什么
| 检查项 | 要检验的问题 | 有用证据 | 常见误判 |
|---|---|---|---|
| 闭环 | 策略能否行动、接收改变后的状态并再次行动? | 策略在环测试和对抗性干预。 | 把开环回放称为仿真器。 |
| 下游迁移 | 模型是否改善规划、控制、学习或数据效率? | 任务成功率、regret、样本效率和稳健迁移。 | 表征分数提高,但决策没有收益。 |
| 校准 | 模型犯错或离开训练分布时,不确定性是否上升? | 可靠性曲线、分布外检测和风险覆盖测试。 | 输出很自信,却不知道失败概率。 |
证据质量层 / 外部人员能够验证什么
| 检查项 | 要检验的问题 | 有用证据 | 常见误判 |
|---|---|---|---|
| 可复核性与访问 | 外部人员能否检查设置、数据切分、指标和失败案例? | 开放协议、代码/模型访问、重复运行和独立测试。 | 只有公司筛选的演示,没有测试协议。 |
不要把九项相加成一个总分。能力、任务效用和证据质量回答不同问题;一层的强项不能抵消另一层缺失的证据。
其中两项检查还可能互相拉扯,这和"互不抵消"是两回事。2026 年 5 月公开的机器人操作基准 MiraBench 会把动作扰动成必然失败——抓握力不足、提前松手、搬运中滑脱—— 再看预测视频是否仍然演出任务成功。按它报告的数字,对一个模型做面向任务成功的后训练,把完成分从 14.0 提到 92.0, 而失败保持分从 48.7 掉到 23.1。这组数字要带两条边界:被后训练的那个模型是基准作者自己在第三方底座上微调的, 所以它证明的是那一套配方,而不是"面向成功的后训练"普遍如此;而在更大的 14B 规模上,同一组对比毫无变化,两边都是 12.8。 底下的失败模式——模型生成训练数据里常见的结果,而不是输入指定的那个——与本站在驾驶仿真里已经描述过的 分布偏置是同一个机制。新的地方在于: 它这次是在动作—结果这条轴上被测量出来,而不只是被描述。
还有一项是上面九项里没有的:它们问的全是模型,没有一项问产出这个分数的工具本身。MiraBench 值得拿来读, 正是因为它公开到足以被检查。它的乐观偏置层由一个视觉语言模型零样本打分,而附录写明用了两套不同的提示词—— 动作条件模型用标准版,文本条件模型用一版刻意放宽的,理由是后者的渲染风格不同。在那张用人工标注检验裁判的表里, 唯一使用宽松提示词的模型,也正是一致性崩掉的那个:人工标为有偏置的案例,它只找回 33.3%, 而所有用标准提示词的模型都在 78.3% 到 100% 之间。整体报告一致性是 87.8%。这些都没有被隐瞒—— 两套提示词、逐模型一致性和完整配置都印出来了——而且漏检会把可靠性分数抬高,不是压低。 另一个研究组的一篇立场论文在完全没有提到这个基准的情况下讲了同一件事的一般形式: 用模型当裁判可扩展、有用,但裁判可能奖励"看起来合理"的结果,同时漏掉与动作相关的错误,因此不该被当作决策有用性的 ground truth。 当一个分数来自裁判时,要问的是:谁验证了这个裁判、在哪些模型上验证的、以及它是否对所有模型一视同仁。
3. 按路线调整权重
| 路线 | 最高权重检查 | 有用指标 | 证据边界 |
|---|---|---|---|
| 视频或世界生成 | 状态、控制、长期一致性、物理保真度。 | 物体保持、几何、干预成功率和随时长变化的漂移。 | 感知分数不能单独证明交互或规划价值。 |
| 可交互生成世界 | 控制、行动后果、闭环、长期一致性。 | 输入延迟、动作响应、状态一致性和策略成功率。 | 可导航演示不能证明适合稳定训练智能体。 |
| 预测表征 | 状态、下游迁移、校准。 | 探针质量、任务迁移、数据效率和分布外表现。 | 表征迁移强,不等于完整场景模拟。 |
| 机器人或驾驶 | 行动后果、闭环、保真度、校准、迁移。 | 轨迹误差、干预有效性、策略 regret、稀有场景覆盖和真机迁移。 | 仿真结果仍只是部署论证中的一层。 |
4. 把三层证据分开
开发者证据
官方发布和技术报告说明在开发者协议下测试了什么。它是一手证据,但不是独立确认。
独立验证
外部复现、下游使用和与现实连接的测试,才能说明结果离开原团队后是否仍成立。
编辑判断
综合判断可以比较路线、指出缺失证据,但不能把官方声明升级成行业事实。
本文属于 C 层,是对 World Model Atlas 已复核公开来源的综合,不是新的通用 benchmark,也没有声称独立复现文中系统。
5. 接受“世界模型性能”之前,先过这份清单
- 模型究竟预测像素、状态、几何、奖励、动作,还是表征?
- 实际任务是什么,哪一种失败最重要?
- 测试是开环,还是策略在环?
- 误差如何随 rollout 时长变化?
- 动作是真正的干预,还是仅仅与未来相关的标签?
- 保真度是否与现实对照,还是只依赖人类偏好?
- 相对可信基线,模型是否改善了下游决策?
- 是否报告不确定性和分布外行为?
- 独立团队能否检查或复现结果?
- 看完全部指标后,仍有哪些结论没有证据?
本站判断
可信的世界模型不是单项视觉分数最高的模型,而是在目标路线需要的干预、时长和下游决策中,表征与动态持续有用, 同时清楚报告不确定性和访问边界的模型。在这些条件可见之前,“世界模型”更适合被视为研究方向或产品定位,而不是已经验证完成的能力类别。
Technical evidence records / 技术证据记录
Evidence table / 证据表
| Claim ID / 判断 ID | Claim / 判断 | Sources / 来源 | Confidence and boundary / 置信度与边界 |
|---|---|---|---|
claim-world-model-evaluation-multidimensional |
Useful world-model evaluation is multidimensional; no single visual metric establishes planning, control or deployment utility. | World Models, Genie 3, V-JEPA 2, GAIA-2 | Medium-high as editorial synthesis; no universal independent benchmark is claimed. |
claim-world-model-evaluation-route-specific |
Evaluation weights should follow the model route and downstream decision rather than one shared leaderboard. | Genie 3, Cosmos 3, V-JEPA 2, GAIA-2 | Medium-high; this is a taxonomy judgment, not a standardized scoring protocol. |
claim-world-model-evaluation-closed-loop |
Passive visual quality cannot establish action-conditioned or closed-loop usefulness. | World Models, GAIA-2, Cosmos 3GAIA-2 Sec. 2.2, p. 6 and Fig. 7, p. 13; Cosmos 3 Table 18, p. 65 and Fig. 22, p. 66. | Medium-high for the distinction; public evidence remains system- and protocol-specific. |
claim-world-model-evaluation-deployment-boundary |
In safety-critical deployment, world-model benchmarks are only one evidence layer and do not constitute a system-level safety case. | RAND, readable PDF p. 10, Koopman & WagnerRAND discussion, p. 10; Koopman & Wagner testing discussion, p. 6 and conclusion, p. 9. | High for autonomous-driving validation; medium when generalized beyond safety-critical systems. |
claim-world-model-evaluation-evaluator-is-audited |
When a benchmark score is produced by an automated judge, the judge is part of what has to be audited: MiraBench scores optimism bias with one VLM but two prompts split by model type, and the one model given the lenient prompt is the one whose agreement with human annotators collapses. | MiraBench, decision-centric evaluation positionMiraBench Appendix D.2.4, pp. 27–28 and Table 10, p. 28; scores stated as evaluator output on p. 8. Position paper Sec. 7.1, p. 21. | Medium-high, bounded to MiraBench as published on 28 May 2026. The benchmark discloses the prompt split and the per-model agreement itself, and its overall reported agreement is 87.8%; the position paper is independent of it but does not mention it. |
Primary and boundary sources / 主要与边界来源
- Ha & Schmidhuber — World ModelsLearned dynamics evaluated through an agent and control task.
- Google DeepMind — Genie 3Official framing and public capability limits for interactive generated worlds.
- Meta AI — V-JEPA 2Official predictive-representation and downstream physical-reasoning route.
- Wayve — GAIA-2 technical reportDriving-domain action-conditioned generation and scenario controls.
- NVIDIA — Cosmos 3 technical reportPhysical-AI evaluations involving action and inverse dynamics.
- RAND — Driving to SafetyIndependent boundary on statistical road validation and simulation's supplementary role.
- Koopman & Wagner — Autonomous Vehicle SafetyIndependent boundary on testing and system-level safety evidence.
- MiraBench (arXiv:2605.29360v1)Action-conditioned failure-preservation protocol and its automated-evaluator configuration. Unrefereed preprint; its authors fine-tuned five of the twelve models it scores.
- Decision-making-centric world-model evaluation (arXiv:2606.15032v2)Independent boundary on treating model-as-judge output as evidence of decision usefulness. Unrefereed preprint; reports no experiments of its own.
Source access and review notes are maintained in Sources and sources.json.