tick 0001 / actor: kestrel · location: the_lower_atrium · goal: find_the_signal · memories: 14

Emergent stories with narritive control.

Just like a physics engine simulates motion, StoryEngine simulates the narrative model of a game world. Narrative designers shape the world and control what is possible. Player actions create persitent, emergent narratives.

Existing narrative systems pre author everything or rely on AI improvization.

Pre authored content cannot truly react to emergent player decisions. AI improvization results in narrative drift, often outside the bounds of your IP.

OPTION ONE

Let the model improvise

A language model freewheels the story. It's expressive, but it drifts: facts contradict themselves, characters forget what they knew an hour ago, and there's no ground truth to check generated content against. Safety becomes a matter of hoping the prompt holds.

OPTION TWO

Branch it by hand

Writers pre-author every path. It's controllable, but it doesn't scale: a few hundred players each making their own choices requires either an exploding tree of authored content, or funneling everyone back onto rails.

A world model underneath. A storyteller on top.

StoryEngine separates the world into two layers. The world layer is deterministic: it tracks who exists, where they are, what they know, and what they're trying to do. The render layer only describes what the world layer has already made true.

The worldSimulation

Actors, items, and locations hold facts and memories. Goals evaluate constantly against the current state, and only complete when their conditions are genuinely met in that state.

ActorItemLocation GoalFactMemoryEvent
The tellingRender

When a goal completes, it can mutate the world and render an output. Mutations change what's true. Renders describe it back, in whatever form a game needs: structured data for game logic, generated dialogue for players. Same state, different audiences.

VideoGame Engine InstructionsAudioText

Every relevant change in the world runs through the same four steps. Watch one event move through it below.

01
Gather
The game sends an event. An actor spoke, moved, picked something up.
02
Evaluate
Every goal relevant to that moment checks its conditions against current state.
03
Mutate
Goals that complete change the world: a memory is gained, a location unlocks.
04
Render
The change is described back, only ever in terms the world now permits.
awaiting event

Narrative designers define the world. Players explore it.

StoryEngine gives unprecedented control to narrative designers to ensure what happens matches your lore, and your IP and your rules.

A FILTER ON TOP

The usual approach

Generate freely, then screen the output. The model can still produce the wrong thing; the filter just tries to catch it afterward.

"...generated, then reviewed."
CONSTRAINED FROM BELOW

StoryEngine's approach

An experience built for younger players, for example, can define rules so that no romantic goal, memory, or fact can ever exist in its world. There is nothing for the render layer to describe, because the simulation never created it.

"...never simulated, so never rendered."

The Consulting Detectives.

A Sherlock Holmes mystery, reinvented as a multiplayer story world built on StoryEngine, and tested against real players.

SESSION LENGTH

15m

average, per session

WAITLIST

45%

conversion to play

REPLAY

>80%

intent to play again

REFERRAL

>85%

would invite a friend

Built for living worlds.

01

Live social worlds

Hundreds of players and characters in the same space, each with a consistent thread, all evaluated together.

02

Emergent narrative games

Stories that take different shapes for different players without an exploding authoring tree behind them.

03

Brand and IP experiences

Worlds that need to feel alive while staying provably on-brand, on-tone, and within defined content rules.

04

Training and simulation

Scenarios where characters need persistent memory and goals that hold up across long, repeated sessions.

Designed for games, by game makers.

Episodes & seasons

Structure content the way a game team already thinks: a season of episodes, a quest per episode, evaluated together for narrative consistency.

Your event types

Define the actions that matter for your game. StoryEngine reacts to the events you send it.

Prompts you author

Voice and tone live in prompts your team writes and versions, evaluated openly against live world state.

Tell us what world you're building. We'll show you how StoryEngine makes it happen.