AlayaWorld, an interactive world model with real-time camera control and long-horizon memory, is now public with inference code and pretrained weights, but not with the code needed to train it. The GitHub repository, which has drawn 878 stars and 36 forks, still lists training code as an unchecked roadmap item. The weights ship under a community license rather than a standard open-source one, and running the model at all requires downloading a gated Google text encoder and a ByteDance depth model first.
Key facts
- Released July 15, 2026 as "inference code and pretrained weights"; training code remains unchecked on the repository roadmap.
- 878 stars and 36 forks on GitHub at the time of writing.
- Requires Google's Gemma 3 12B text encoder, which is gated behind accepting Google's license, plus ByteDance's Depth-Anything-3 code and weights.
- Weights are distributed under the LTX-2 community license, so commercial use is conditional rather than open-ended.
The technical idea worth understanding is how it remembers. A world model generates a navigable environment frame by frame, and the classic failure is that walking away from a room and walking back produces a different room. The model has no persistent representation of the place, only a rolling window of recent frames, so the scene is quietly reinvented each time. Anyone who has watched an AI-generated video fail to keep a character's shirt the same color across ten seconds has seen a small version of the same problem.
AlayaWorld's answer, in the repository's own description, is "two forms of complementary memory: an explicit 3D cache reprojected to the queried view for spatial recall, plus a compressed frame-history embedding for temporal continuity, so revisited places stay recognizable." Those are two different jobs. The 3D cache is a geometric record of where things are, re-rendered from whatever angle you are currently looking, which is why a room survives being left. The compressed frame history handles the shorter-range problem of motion looking continuous rather than stuttering between plausible states.
The second mechanism addresses drift. Autoregressive generation compounds its own errors, because each frame is conditioned on the slightly-wrong frame before it, and over a long rollout the small errors become a melted, saturated mess. The repository describes "long-horizon stability from training on drifted histories and an error bank that re-injects accumulated artifacts into both memory and target, preventing errors from compounding over minute-long rollouts." In plain terms, the model is deliberately trained on its own corrupted output so it learns to recover rather than only ever seeing clean inputs. It is the difference between a driving student who only practices on empty roads and one who practices recovering from a skid.
The release itself is where the caveats concentrate, and they are the kind that decide whether a model is genuinely useful to outside researchers. Inference code plus weights means you can run it. No training code means you cannot reproduce it, cannot verify the training claims independently, and cannot adapt the method to your own data without reimplementing the paper. The LTX-2 community license means commercial use comes with conditions rather than freedom. And the dependency chain is unusually awkward: to run one lab's open model you must first accept Google's license terms for a gated model, then fetch a third company's depth estimator and its weights.
A further honest note about sourcing. The associated papers, an introductory paper at arXiv:2607.06291 and a fuller technical report at arXiv:2607.18367, describe additional mechanism details including a bounded rolling context designed to keep per-chunk compute constant so the rollout horizon is in principle unbounded. Those specifics could not be independently re-verified in this pass because the full text was not retrievable, so they should be read as the authors' claims rather than as checked results.
The pattern this fits is now familiar enough to be predictable. July's wave of world models produced a similar split, where the most commercially credible system kept a real game engine running the physics and used AI only to restyle the frames. MiniMax shipped H3's weights while keeping the quality-critical input stage hosted. In each case the release is real, the code runs, and the openness has a shape that the word "open" does not convey on its own.
For anyone evaluating one of these releases, the questions worth asking are consistent: is the training code there, what does the license actually permit at your revenue, and how many other companies' licenses do you have to accept before the thing starts. AlayaWorld answers those as no, conditionally, and two.
Background: our lessons on world models and open-weight models.
Originally published on Ground Truth, where every claim is checked against the primary source.
