SEREN AI is a Dungeon Master. You play one character. It runs the world, every NPC, and the two or three companions who make up the rest of the party — inside a canon it never loses. One human, one character, no other people at the table.
You give it the bones — structure, beats, characters, factions, your own items and spells and rules. What happens between those bones is improvised at the table, by a DM that knows the world. Which means the same material never plays out the same way twice.
The hard part of playing alone is not the world. It is that nobody at the table surprises you. SEREN runs the two or three companions beside you as people, not as options — they want things, they have opinions about what you are doing, and they act on both.
A companion can go ahead without you, hold something back, or settle a problem in a way you would not have chosen. You find out afterwards, like anyone at a table would.
You cannot pick their next line or spend them like a resource. They carry their own wants, and those wants do not always agree with yours.
Trust is earned and spent. What you did in session four is still what you did, and the person who watched you do it has not forgotten.
The party is not an extension of you.
Going off script isn't a failure mode of tabletop. It is the whole appeal. You will always do the thing nobody prepared for — and a system that only knows the plan treats that as an error. It refuses, it railroads you back, or it quietly drops the thread and pretends the detour never happened. SEREN takes the detour as canon and keeps building from there.
Three prepared sessions, gone. Every scripted beat now points somewhere you aren't.
The chaos is the story. SEREN builds it with you.
A campaign in SEREN is not a transcript. It is a world — characters, factions, locations, objects, rules, secrets, consequences, unresolved threads, an evolving canon — and SEREN improvises freely inside it while keeping every part of it coherent, session after session.
It works in chat. There is no application to learn and no dashboard to maintain. And it is a Dungeon Master, not a playback device: it takes the bones and makes the calls in the moment — never asking you to remind it what already happened.
SEREN maintains those relationships.
You never open a session by explaining the world back to the machine. It already knows, and it knows what changed last time.
Ser'en is a level 11 Circle of Stars druid. She is also someone with a debt, a grudge and a reason to distrust Kestrel. SEREN holds both, and neither contradicts the other.
Knowledge is tracked per person. An NPC cannot react to something they were never told, and the world cannot leak what you haven't earned.
Most tools fuse the story, the rules and the current situation into one long conversation. SEREN separates them. That separation is the whole architecture — and the reason the system isn't bound to any single game.
Canon, characters, places, factions, history, secrets, the things that are simply true. Imported, or grown at the table.
D&D 5e, with house rules treated as canon. A ruleset is a layer, not the foundation — which is why it can be swapped.
Every change the party caused, who witnessed it, what it cost, and what it set in motion. Live, and carried forward.
D&D is where SEREN starts. It isn't where SEREN ends.
Because the world, the rules and the live state are separate concerns, the architecture doesn't care which game you're playing. A science-fiction setting, an original universe, a system of your own — that is where this is going. Today it runs 5e, and it runs it properly.
How the three layers work →One decision at the table doesn't resolve. It propagates — through people, places, factions and time — and the world goes on acting on it while nobody is looking.
SEREN doesn't forget the consequences just because the session ended. Nobody had to log any of this.
Factions move between sessions. Unclaimed power gets claimed. The world has business of its own and gets on with it.
Structure, beat sheet, characters, factions, the shape of an ending — plus every custom item, spell, race and ruling that has been invented. Not dialogue. Not scene text. You are handing over a skeleton and a rulebook, and SEREN puts the flesh on it live.
This is not a form to fill in. Nothing here has to be written in SEREN's format, or written again at all — it is a list of what the game needs to know, and most of it is already sitting in your notes.
SEREN holds the skeleton as canon and plays everything else live — dialogue, reactions, complications, the timing of a reveal. The structure survives. The session is still a surprise.
Work done once stays done. The village built in session two is still there, still populated, still remembering how the party behaved in it.
House rulings become part of the ruleset rather than something re-argued every week. If you wrote it down, it is the law.
Bring the bones. SEREN runs the game.
Three anchors, written once. One person, playing them twice, months apart. Nothing below was authored — and both playthroughs are faithful to what was handed over.
Every anchor was honoured. Neither campaign was written. This is what a DM does, and it is what a script cannot.
The split isn't judgement against bookkeeping. It is what can be known exactly against what has to be inferred — and one column that belongs to nobody.
Everything that has to be inferred in the moment. This is the DM's work, and SEREN does it.
Nobody overrules the dice. Not the model, and not you.
A roll can be interpreted. It cannot be reversed. One test: did the success or failure state change? If it did, someone cheated.
One character, played properly, in a world that will not bend to make you comfortable.
Most campaigns don't die from bad ideas. They die from calendars. The world got finished, the group didn't survive the year, and the folder has been sitting there ever since — a bible, a map, forty pages of notes, and no way to find out whether any of it works.
Seren reads what you already made. Hand it the bible, the notes, the wiki, the half-written sourcebook. It works out what things are called, what is true in your world, and what you have and haven't decided — and then it asks you the questions you never had to answer, because you never got to the table.
You don't restructure any of it. The import turns the corpus into the world, the ruleset and the beats, and hands them back for you to correct. Your notes stay your notes.
Then you play it. Not pitch it, not finish it. Play it, this week, as one character, and find out which parts land. The players you could never get to a table are the ones sitting beside you.
And then you release it, if you want to. Worlds, campaigns, items and characters, shared with the world. A campaign is a zip of Markdown files — email it, post it, hand it to whoever wants to run it. For a lot of creators the joy was never playing it themselves — it was watching somebody else play it.
You can finally find out whether it works — without booking four people.
A world bible has setting and no plot. Naming and canon can be read out of what you wrote; the beats cannot. Those have to be asked for. This part is an interview, not a parser.
SEREN AI is being built, and as of 27 August 2026 it has run one full session — published with its dice, its records and the two rolls it lost. The files it runs on are here. If you have a world you’d bring to it, or you build systems and want to tell me where this one breaks, write to me.