Database
Beyond Temporal Proximity: Explanatory World Models for Credit Assignment in Reinforcement Learning
arXiv cs.IR0 views
arXiv:2610.13504v1 Announce Type: cross Abstract: Generative Recommenders increasingly use Reinforcement Learning (RL) to optimize outcomes that may appear hundreds or thousands of interactions after a decision. Standard RL propagates reward according to temporal proximity rather than explicit relevance, attenuating the signal assigned to distant but important actions and creating a source of sample inefficiency. We introduce Explanatory World Models (EWM), an attribution framework that uses explanations to identify the earlier events that plausibly contributed to a realized outcome. We instantiate EWM with a frontier language model and use its explanations as learning signals using a conservative hierarchical operator that recursively redistributes reward while preserving the undiscounted episode return. To investigate what constitutes a useful explanation, we operationalize three complementary variants inspired by Halpern's actual causation, Lombrozo's explanatory simplicity, and Deutsch's hard-to-vary explanations. We evaluate EWM on two controlled long-horizon RL benchmarks, a public sequential-recommendation benchmark, and an industry-scale generative recommender. On Crafter and WordCraft, EWM substantially outperforms PPO and LaRe, with its largest gains when rewards are most delayed. On KuaiRand, EWM outperforms SFT and LaRe offline and A2C online. Finally, in an offline evaluation of an industry generative recommender, EWM considerably improves Recall and increases behavioral proxies. These results suggest that explanations can provide structured and reusable credit for learning from delayed outcomes.
Source:https://arxiv.org/abs/2610.13504PreviousWeb$hell: A Unified Interface for Agentic Web AccessNextRATED: Reliability-Aware AI Agent Tool Retrieval via Execution Dynamics
Related posts

🧠 Do Prompt ao RAG: como fazer um LLM responder sem inventar (e sem processo do cliente)
0dev.to Java
How I built an AI Contract & Scope-Creep Shield for Developers (and hit a 98/100 Staff SDET QA score)
0dev.to JavaScript
ToGO for Laravel developers: the artisan commands you know, in Go
0dev.to Go
The database log that filled up and stopped every CircleCI pipeline
0dev.to Database
61% more Postgres backports: I recounted the delay
0dev.to Database
How to upgrade Postgres in Docker to 18, and be ready for 19: dump and restore or pg_upgrade --link
0dev.to Docker