Prep that survives contact with the table.

The notes problem, stated plainly.

Session prep usually lives in a document written the night before, already a little wrong by the first roll. A wiki page nobody opens once the dice start moving. A folder of random tables printed out and rarely reached for once a fight gets loud. None of it is built to change shape once play starts, so it doesn't.

What actually changes the story happens at the table: the NPC who died a session early, the faction that overheard something they shouldn't have, a promise a player made and will be held to later. If nothing at the table is built to catch that, it survives only as long as your memory does, and the next session's campaign notes start from what you wrote before, not from what actually happened.

Plan the night from the world, not from a blank page.

Every session's agenda is built from scenes already sitting on your timeline, the same graph where relationships move through phases and every scene already knows what changed before it. Add a scene to the agenda once and it can only be planned into one session at a time, so two nights can never quietly claim the same content. Don't finish it at the table? It splits forward into a later session, carrying your note on what was played and what's left, so campaign prep never restarts from zero.

What happened is captured where it happened.

Log what happens without leaving the table. A one-row composer sits in the session runner: a note, a decision, a meeting, a reveal, a roll, logged in whatever order the night actually goes, each one carrying a mark for its own kind so the log stays scannable the next morning.

Secrets live on the entities that hold them, not in a separate binder, and you reveal one exactly when the party earns it: the traitor's name, the location of the vault, whatever the old god actually wants. Revealing it logs itself as a reveal entry, right where it happened, and the rail beside the log flips from Prep to What's true the moment you start, so the story so far is always the read in front of you.

The recap writes itself.

Star a log entry as it happens and it becomes a beat; skip the ones that were only logistics. At the end of a session, StoryVue assembles a chapter from what you starred: what happened, who the party met for the first time, and what they learned, in the order you actually played it. Nothing is generated. The chapter is your own log, read back.

Mark any entry player-facing and reword it if the table's version should read differently from your own notes, then print the player copy with every GM secret left out. That whole mechanism, GM copy or player copy, is what the campaign journal page is for.

The fight is part of the record.

End a fight and StoryVue pre-fills an editable outcome: who went down, what the party walked away with, how it actually ended. Confirm it and that summary logs itself into the running session exactly like everything else that night, so it reaches the chapter and the printed recap with no separate write-up. A table roll works the same way: pull one from the session composer and the result logs itself right where you rolled it.

Building the roster, checking the balance, and running the turn itself all live on the encounter builder page.