Inside a published 5,011-turn AI RPG world record.

Memory is more than one mechanism

A transcript-only setup keeps the available story inside the model's active context. Dedicated AI RPGs can also use summaries, memory banks, embeddings, authored lore, and structured state. When retrieval or state tracking misses, a merchant you robbed early greets you like a stranger later. A faction you dismantled is running the city again. The world does not break in one loud moment. It drifts, and it drifts worse the longer you play, because a roleplaying campaign is the longest-running test for any long-running system.

A memory label on its own does not describe what is stored or enforced. Ask which mechanisms are active, run a repeatable callback probe, and inspect any records the service makes available.

So we published the receipt

We drove one world to turn 5,011 and published a frozen event artifact. It includes the player action and displayed mechanical receipts for indexed turns, not every raw prompt, response, and database row. You can read the 5,000-turn record right now and page through it yourself.

The run was piloted by an automated player, which is the point: no human patience required, and nothing staged. When we say “verified,” we mean the server's own records at turn 5,011 were checked against the start of the run, and the cast, factions, quests, and locations were all still there in the audited categories, with zero rows lost. The check is mechanical. It does not run through the narrator's confidence at all. That is a result from this artifact, not a universal memory guarantee.

Four turns from the record

Here are four turns from that campaign, pulled from the published artifact. The first two show displayed receipts. The last two, four thousand turns apart, show what it brings back.

Then, deep into the run, we asked the same question twice. Once at turn 1,010, and again four thousand turns later.

The same named collector, Vasska's, comes calling at turn 1,010 and again at turn 5,010. Four thousand turns apart, the debt was still a live thread the world could answer to. That is what a record buys you: a thread does not have to survive in the narrator's memory to still be on the books thousands of turns later.

Every one of those turns sits in the public record, in the order it happened, next to the roughly five thousand others.

Claim versus proof

Here is what to separate when you inspect this artifact.

How to tell if an AI RPG's memory is real

You do not need our word for any of this. Test any AI RPG the same way, ours included.

1. Set a specific fact early. A debt you owe, a name you were given, a promise you made.
2. Play a long stretch. Long enough that the early scene has scrolled far out of view.
3. Leave, then come back. Closing the tab tests cross-session storage, but it does not require the world to generate scenes while you are away.
4. Ask about the fact. If the world holds it without you re-explaining, it is useful evidence. Repeat the test before drawing a broad conclusion.

That is exactly the test our public record already ran, in the open, past turn 5,000. The debt asked at turn 1,010 was still on the books when the collector returned at turn 5,010.

What “verified” means, and what it does not

Two honest caveats, because a page like this loses its point the moment it overreaches.

First, on scope. This is proof of persistence, verified at turn 5,011. It is not a claim of flawless recall at every single moment of the story. The narrator is still a language model, and it can phrase something loosely or color a scene in a way you would have written differently. That is exactly why we do not let it own the truth. When the prose gets loose, the record does not move.

Second, the artifact is not an independent third-party audit. It was produced and checked by Creation OS against its server records. The published files make the stated result inspectable, but they do not expose every internal input or establish performance against another service.

Questions people ask