How a campaign survives past session five without forgetting who you are, what you broke, or who died.
Most tools fail at the same place, for the same reason: everything lives in one chat history. Canon, mechanics and current events all compete for the same context, and the longer you play the worse the competition gets. SEREN separates the engine into three concerns that never pollute each other.
Each layer answers one question and holds one kind of truth. Nothing in the world file changes because of a dice roll; nothing in the ledger argues with the rulebook. That boundary is what makes long play possible.
The bible. Factions and how they move, history, geography, characters, and a separate ledger of who knows which secret. Static files, injected when something in play actually references them — not carried in full, forever, as conversational sediment.
5e today, with house rulings treated as part of the ruleset rather than as suggestions. The model narrates and adjudicates intent; the arithmetic stays bounded — DCs, damage, resources, the difference between a success and a failure. A ruleset is a layer over the architecture, not the architecture itself, which is why another system can sit in the same slot.
Everything that has happened and everything it set in motion. Faction positions, uncollected debts, who died and who knows they died, what was promised, what is still open. It updates as you play, in the background, and it keeps advancing between sessions — which is why the world has news for you when you come back.
Canon doesn't drift, because the thing that changes isn't the thing that's written down.
This normally breaks things — a character walks into a campaign built for a different power band and either trivialises it or evaporates. It breaks because most systems store the character and the world in the same place, so a mismatch has nowhere to be resolved. Here, the character is state and the power band is ruleset, and the two are reconciled rather than merged.
Encounter maths, faction caution and what people are willing to try against you are read off the state, not fixed at authoring time. The threats change hands. Nothing in the world file is rewritten to accommodate you.
The campaign is not scaled down to meet you. What changes is which doors are open, who will speak to you, and how far you get before the world notices — which is the honest answer, and the more interesting one.
Prices, scarcity, distances, what a favour costs and what a life is worth stay internally consistent. A powerful character is rich relative to the setting; the setting doesn't inflate to match.
Migration is a reconciliation, not a rewrite.
Bringing a character in means resolving three things: what the ruleset says they can do, what the state says they've done, and what the new world already holds as true. Conflicts surface as questions rather than silent overwrites. Nothing is quietly deleted to make the numbers line up.
There is no opaque memory to trust. The world, the ruleset and the state are structured Markdown — inspectable, correctable, diffable, and yours. If SEREN got something wrong, you can find the line and fix it.
Every change to the state is written down as a change, not absorbed into a summary. You can see when a faction moved and what moved it.
Plain text in, plain text out. Back it up, version it, hand it to someone else to run. Your notes stay your notes.
A wrong fact is an editable line, not an argument with a model. Fix it once and the world is fixed.
SEREN AI is being built, and it has now run one full session against this architecture — which found four things wrong with it in an evening. The files are published. If the architecture is the part you care about, write to me — that’s the conversation I want to be having.