The World-Model Qualification Test › Limitations and Impact
World Models HandbookAll chapters The World-Model Qualification Test › Limitations and ImpactOne section · Sections in this chapter10 / 12 ↓
Reading tools Definitions & inline links
Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.
Article links
Make inline references clickable
The qualification test earns its keep by catching failures that loss curves miss, but it is worth stating plainly what it does not settle. The four criteria are necessary, not sufficient. A model can pass every test we ran and still fail in deployment: our experiment used a linear plant, dense random exploration, a known reward, and a planner matched to the model's interface. Real systems violate all four comforts at once. Partial observability can be structural rather than incidental, with hidden variables that no finite history window reconstructs. Exploration budget is scarce, so the wide-coverage data that secures action conditioning may be expensive or dangerous to gather. And the planner itself introduces a moving target: improve the optimizer and you change which regions of the model get stressed, potentially invalidating yesterday's qualification.
Each of these violated comforts is worth naming concretely, because together they sketch the gap between this chapter's laboratory and industrial practice. Structural partial observability means the belief-state remedy may require a posterior over high-dimensional or poorly modeled hidden variables, where our cart needed only a scalar velocity. Scarce exploration means the random-action luxury must be replaced by carefully engineered excitation signals, safe exploration algorithms, or transfer from simulation, each of which reintroduces the confounding we sidestepped. And the moving-target problem means qualification is a recurring activity tied to the deployment configuration, not a certificate issued once at training time. Organizations that treat model evaluation as a launch gate, rather than a continuous process coupled to the planner and the data pipeline, rediscover this lesson the expensive way.
There is also a deeper conceptual limit worth naming. Decision usefulness is relative to a task, so "qualified" is never a global verdict. A model that regulates a cart to the origin may be useless for tracking a moving target, and a model superb at half-second video prediction may be unusable for minute-scale planning. Practitioners therefore qualify models per deployment envelope: a declared region of states, actions, horizons, and tasks within which the four criteria have been verified. Outside the envelope, all bets are off, and a central engineering discipline of Part XII is building agents that know where the envelope ends.
The envelope concept deserves a final elaboration because it reframes what a "qualified model" document should contain. A serious qualification record specifies not just scores but scope: the state regions probed, the action ranges tested, the horizons rolled out, the reward structures evaluated, and the baselines compared against. Two teams declaring "our model passed qualification" may have verified disjoint things, and only the envelope descriptions reveal it. This is the same discipline that structural engineering applies to load ratings: a bridge is not "strong," it is strong for stated loads, and the sign stating the limit is part of the safety system. Agents that monitor their own distance from the qualified envelope, and degrade gracefully or defer to humans when approaching its edge, are the subject of Part XII.
These limits explain why the qualification test is a recurring motif rather than a one-time gate. Every major lineage in this book, from system identification through model-based RL to foundation-scale video models, rediscovers the same four questions in its own dialect, and each generation of architectures shifts the frontier of which failures are easy to catch. What the test provides is a shared language for those conversations: when someone reports a new world model, the productive questions are always the same four. What is in the state? Do actions cause anything? Where do the predictions stop being trustworthy? And does the model improve behavior?