Structured narrative engine
Two things every story has. Most tools track one.
StoryVault puts your scenes on a numeric clock and keeps causality as a separate graph on top — so a flashback is a position, not a workaround.
Why a board, and not a document
A word processor only knows one order. A story has two. Scenes sit on a numeric clock: an anchor event at zero, the past negative, the future positive. Causality is a separate directed graph laid over the top. Keeping them apart is what makes a flashback simply a scene at T−206 that something at T+3 depends on, rather than a formatting problem.
Axis one — when it happened
Every scene carries a position on the clock and a duration. Move one and the timeline re-sorts; nothing else has to know.
Axis two — what it depends on
Causal edges form a directed acyclic graph, held to a strict rule: a cause must finish before its effect begins. Break it and the engine says so.
The consequence — restructure without rewriting
Reorder the telling and the dependencies survive, because the two were never the same list to begin with.
Coming to mobile
The board, in your pocket — iOS and Android, 1 October 2026. Built for Shipaton 2026.
This page needs JavaScript for the interactive board. The text above is the whole of what it says.