Curated, not generated: how a world gets written

"Hand-authored" is doing a lot of work in our tagline, so here's the audit. A world in Unwritten is not a prompt with a nice paragraph of lore. It's two structured documents: the world itself — cast, factions, enemies, companions, situations, secrets, rules — which never changes during play, and the starting photograph of your character, which changes every turn. Everything the engine does at runtime, it does by reading the first and rewriting the second.

A frame, not a script

The counterintuitive part of writing for an AI narrator: you cannot write a plot. The narrator won't follow scene twelve with scene thirteen, because the player just did something scene thirteen never anticipated. Write a script and you'll watch it die by turn six.

What you write instead are materials — situations, antagonists, revelations, places — that the engine injects when the story reaches the right conditions. Even the guidance is written with that humility: the hints that pull a story toward its authored heart are, per the style guide, magnets, not orders. An evocative gravitational phrase, never "the player must".

Progression works the same way, on two rails. A scalar one — rank points, earned through accomplishments — and a structural one: beats, verifiable narrative facts that open the passage from one act to the next. And beats obey the house rule that governs the whole engine: they're detected by the backend or by a dedicated classifier reading the finished scene — never by asking the narrator to remember to raise its hand.

Five passes, because one produces mush

No world is generated in a single pass, by us or by anyone. The pipeline is five sequential passes — skeleton, then cast, then situations, then mechanics, then the weave that ties every thread to every other — each one taking the previous output as its raw material. The quality lives in that sequencing: depth is what happens when the fourth pass has to be consistent with three passes of prior decisions.

The reviewer's rulebook

Then a human reads it against a short, brutal list. The rules are quotable because we actually quote them at each other:

• The central secret is an onion. Each act peels one layer, and the last layer must recontextualise the first. If the secret can be summarised after act one, it's too thin. Ship nothing whose ending is merely the beginning, repeated louder.
• No orphan backstories. Every significant character connects to at least two other threads — a faction, a companion, an old wound. A character wired to nothing is trivia.
• Situations are dilemmas, not quests. Every predicament must admit at least two strategies that anger different camps. If every outcome pleases the same people, it isn't a choice; rewrite.
• The complication is a gift. A failed roll must deliver something — a revelation, an escalation — that makes the story better for having gone wrong. "It doesn't work" is banned as an outcome. This is the authoring side of the fail-forward dice.
• An enemy is one sentence of gameplay. If its signature mechanic doesn't change how you fight it, it's a bag of hit points. Rewrite. (The engine holds the mercy rule at the other end: opposition weak enough falls to a single decisive action instead of three dutiful rounds.)
• Companions carry red lines. An arc, and at least two lines they will not cross — written before the world ships, so the moment you push one is authored, not improvised.

The tone contract

Every world also signs a contract about how it feels: five adjectives it must always be, three things it must never do, and an accent colour the entire app dresses in while you're inside. A gothic manor and a tower-climb power fantasy shouldn't feel like the same product wearing hats — so the interface, the narration and even the loading lines (yes, those are authored too, in-world, per scenario) belong to the world you're in. The "never" list matters more than the adjectives: a world that knows what it refuses to do is a world that can be trusted with its own dark corners.

The gate at the end

Finally, no world ships on good intentions: an automated validation pass has to go green. Most of what it catches is plumbing — dangling references, a beat pointing at an enemy that doesn't exist yet, structures malformed in ways that would fail silently mid-adventure. The subtlest check is economic: an act must contain enough authored material to be exitable. Too few situations against too high an exit bar means a player could consume everything written and stand in a room with no doors — solvent-looking, quietly bankrupt. That's a blocking error, discovered the way most of our rules were discovered: by shipping close to the line once and not enjoying it.

It's a lot of process for something players never see. But that's the bet the whole product makes — fewer worlds, built deeper — and depth, it turns out, is mostly discipline wearing a nicer word.