How the recapsare made
The map is hand-built
Every game starts as a hand-made map: the story is split into ordered beats — chapter-sized story points — cross-referenced from published game guides and wikis, one game at a time. Each beat gets a spoiler-light label you'll recognize if you reached it, and a full, spoiler-heavy reference summary that never leaves our server. Quest names are indexed by hand too, and each maps to the last beat you've provably finished — so searching a quest can only ever under-reveal, never spoil.
The writer never sees your future
When you mark where you stopped, our system slices the story at that exact point and hands the AI writer only the beats you've already played. The events after your save point are never in the room. This is the part we want to be loud about:
Spoiler-safety isn't a filter that scrubs the output. The recap can't spoil what it was never given.
One more guard: the “where you are now” line in every quick recap is pinned to our own hand-built chapter data — never to the AI's memory of the game — because a model that knows the whole game from its training could otherwise name a chapter you haven't met yet.
Checked before it ships
Every recap is pre-generated and then run through an automated QA scan that hunts for two kinds of failure: spoilers that leak past their beat, and story details that don't match our reference summaries. The scan has to pass with zero must-fix findings before anything is deployed. Nothing is generated live on your visit — you read exactly what was checked.
Readers keep us honest
Under every recap there's a “something wrong? flag it” link. A flag points us at the exact game, chapter, and version you were reading; we fix the underlying story data and regenerate that recap — usually within a day. Because everything is generated from our hand-built map, a mistake is fixed once, at the source, for every save point it touched.
The voice is AI — and labeled
Where narration exists, it's an AI voice, and the player says so right on the label. It never autoplays; it reads the same checked text you see on screen, word for word. We'd rather be upfront about the trade than pretend a human narrator recorded hundreds of save-point-specific retellings.
More on the philosophy behind all this on the about page.