{
  "title": "Memory read before update",
  "caption": "In the classic V–M–C design, the controller reads current visual code z_t and memory h_t to select a_t. The recurrent memory then updates from z_t and a_t. The controller does not directly receive the memory model's next-code prediction. Author-created explanatory diagram. Playback time is illustrative and is not measured runtime.",
  "alt": "V–M–C flow: visual code and recurrent memory select actions, and memory updates occur independently of environment execution.",
  "sources": [
    {
      "path": "content/blog/2026-06-09_world-models-for-embodied-ai/post.md",
      "description": "Article mechanism and retained citations"
    },
    "https://worldmodels.github.io/"
  ],
  "limitations": [
    "This playback is an example. Playback duration is not measured runtime.",
    "Environment execution and memory update use the same action. Their positions are not a mandatory hardware schedule.",
    "The recurrent cache is different from a prediction of the next visual code."
  ]
}