New Forms — Stories That Watch You
Branching narrative never died from a lack of technology. It died from word count. Once the cost of prose collapsed, the ceiling on flags disappeared — and a form that was previously impossible became buildable. Three finished works, with the code.
Everyone who has played an interactive story has had the same daydream: a story that remembers every choice you made and confronts you with it at the end. On paper it is trivial — keep some flags, branch on them.
Almost nobody actually did it. The obstacle was never technical. It was volume.
Add one choice and you need two versions of everything downstream. Stack three and you need eight. A human writes a finite number of words, so even commercial studios landed in the same place:
Branch, then merge immediately.
Keep choices as cosmetic variation. Keep the spine of the story single-threaded.
I followed that rule myself when I wrote Outside the Answer — 15 episodes, about 139,000 characters of Japanese. I followed it because otherwise I would not have finished. "A story that remembers you" was blocked by manuscript volume, not by imagination.
This is worth stating precisely, because the sloppy version of this claim is everywhere. AI does not make a story good. Structure, pacing, and where the reader is supposed to break — a human decides those, or you get something competent and forgettable.
What dropped is one thing: the unit cost of producing text. And that single change rewrites the design space, because the volume wall was the only reason flags had a ceiling.
| Before | Now | |
|---|---|---|
| Number of flags | A handful (whatever code can manage) | Effectively unbounded |
| Granularity | "entered route A" | "went quiet at this one line" |
| How it surfaces | A different ending | The narrator's tone in the same scene |
| Cost to the writer | Combinatorial explosion | Decide a policy, then fill |
Row three is the one that matters. When flags are cheap, branching moves from "jump to another route" to "the same road, told differently." From the reader's side that does not feel like a fork. It feels like the narrator is looking at you.
Three properties, that is the whole definition:
The third one is the point. Metafiction used to be a matter of craft — something a particular author could pull off. When you can hold thousands of cheap flags, it becomes a standard feature you can implement. The fourth wall is now a design decision, not a talent.
The thing that actually worked in implementation was not storing flags as booleans. Give every beat a stable identifier, record that the reader passed through it, and read it back later. The prose itself becomes the state.
// Give each beat an id — for recording, not for branching
{ ix: 137, n: 'Mia', t: '"Probably not."' }
// Record the pass-through. What was read IS the state.
seen.add(b.ix);
// Read it back — change the telling based on what they saw
const line = seen.has(137) ? L.t[212] : L.t[213];It looks unremarkable. The difference from before is that this does not fall apart at several hundred of them, because a human no longer has to hand-write every variant. What changed is not the code — it is that adding a flag stopped feeling expensive.
The lesson from actually shipping this: reacting too often ruins it. If the story acknowledges the reader constantly, the reader stops watching the story and starts watching the mechanism.
What lands is staying silent for a long time and then naming them exactly once. Hold thousands of flags. Fire a handful. That is the current conclusion.
A hero who has killed the Demon Lord goes through the Lord's "Catalogue of a Hundred Sins," one entry at a time. The text you are reading is itself the forbidden book the hero wrote — and the final line is addressed to you. About 30 minutes. Seven languages. Fully voiced in Japanese and English. Free, in the browser.
Read it in English15 episodes, 1,593 recorded voice lines. Each episode ends with a letter, and at some point someone reading along starts writing in the margins. On a second playthrough every letter turns out to have been a conversation.
Open itOn an island where fallen stars wash up as fragments of language, you collect words and splice them into the gaps in the text to re-weave the story. "Words are the state" turned directly into the verb of the game.
Play it| Symptom | Cause | Fix |
|---|---|---|
| One line has no audio | Voice filenames are hashes of the line, and the line was edited by one character | After every revision, machine-count it: references = files on disk, 0 missing, 0 orphans |
| Every translated version renders in flawless Japanese | The "fall back to the original when no translation exists" path was hiding an undeployed script file | Verify against the live URL, never the local server |
| The trick feels cheap | The "I remember you" moment fires too often | Fire a few times. How many you hold and how many you use are separate decisions |
Every failure listed above throws no error. In AI-assisted production, the time sink is not crashes — it is the ways things break while continuing to look finished.
More of these are collected in New Forms Research (Japanese, for now — English versions are being added). Everything is free and runs in a browser: the shelf.