What Happens When You Press Send
The pipeline behind every SagaBound turn: safety check, context assembly, narration, a separate rules pass, and the codex update.
Updated July 23, 2026
Every turn you send runs through a short pipeline: a safety check, context assembly from your story's memory, the storyteller model writing the scene, a separate rules pass that turns prose into game state, and a codex update. Each stage exists to keep the story fair, consistent, and yours.
Step 1: the safety check
Before the story sees your action, a dedicated safety classifier reviews it against your saga's maturity rating. Safe games are held to the strictest line, adult-verified Unfiltered games to the widest one, and anything outside the Acceptable Use Policy is declined with a message rather than silently eaten.
Step 2: assembling the scene
The game gathers what the narrator needs to write this specific moment: your recent turns word for word, your character sheet and active quests, the codex entries relevant to the scene, and any past moment that long-term memory judges relevant by meaning. Getting this selection right is most of what keeps a long saga consistent.
Step 3: the storyteller writes
The storyteller model you picked in Settings writes the scene, bound by your mode's contract: Adventure narrates around real stakes, Storyteller mode stays purely narrative, and Tabletop must narrate exactly what the dice decided. It reads typos charitably, keeps your character's inner voice yours to write, and stays inside the fiction instead of explaining game mechanics.
Step 4: the rules pass
A separate, faster model then reads the finished prose and extracts what actually changed: damage taken or healed, items gained, dropped, or destroyed, money spent, ground covered, quest progress made. Storytellers embellish; bookkeepers must not. Splitting the jobs means your health bar and inventory come from the bookkeeper, never from a dramatic turn of phrase.
Step 5: the codex keeper
Finally, the codex is brought up to date. New people and places get entries, changed facts update existing ones, and near-duplicates are merged by identity rather than spelling, so the captain you met under a nickname stays one person. Everything lands in one autosaved state; see saves and progress.