Event-Conditioned Diagnostics of Kinematic, Contact, and Object-Permanence Structure in Passive Object-State World Models

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2606.28455v3 Announce Type: replace-cross Abstract: World models can predict future physical states, but prediction accuracy alone does not explain how physical information is organized and used inside their latent dynamics. We introduce a controlled diagnostic protocol for studying event-conditioned latent physical structure in passive object-state world models. The protocol separates three questions: whether event-regime information is readable, whether event context changes the relative emphasis of kinematic-, contact-, and object-permanence-related readouts, and whether suppressing readout-aligned directions affects prediction. Using a balanced controlled-generator dataset with free-motion, collision, and occlusion events, we evaluate GRU, Transformer-lite, and RSSM-lite transition models under a fixed-horizon forecasting setup. Across three independent seeds, all three architectures learn useful predictive dynamics and support reliable event-regime readout. Event context systematically shifts the relative readout pattern: free motion is kinematic-dominant, collision increases contact-related structure, and occlusion increases object-permanence-related structure. Time-aligned analyses show corresponding phase-related shifts. Fixed-horizon projection Causal Field Effect (CFE), used here as a functional-sensitivity test, gives the clearest evidence for contact-aligned structure in collision-contact windows. Object-permanence-aligned structure is also sensitive during hard occlusion, but control specificity remains mixed. These results support event-conditioned …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2606.28455
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.