Skaldborn
A generational life-simulation MMO. You don't play a character — you live a life inside a world that keeps evolving with or without you, then a different life when that one ends, and another after that. The world remembers what you did in each of them.
Most games reset between sessions. The story exists in your save file. The world is the stage. Skaldborn flips that. The world is the protagonist. You — and every other person in it, players and NPCs alike — are participants in a history the world is writing in real time. When your character dies, the simulation doesn't pause; it advances. The next life you start may be your great-grandchild, or a stranger in the settlement your last character helped found, or a peasant in a region you've never seen. Across many lifetimes, you accumulate something most games can't offer: a personal entry in an evolving history.
How it's different
The world remembers everything
Villages remember founders. Cities remember tyrants. Families remember ancestors three generations back. A rivalry between two NPCs that started over a stolen plow can shape the political landscape their grandchildren grow up in. The world remembers everything is the first design principle in the spec — an architectural commitment, not flavor copy. Nothing important disappears because of an engine constraint.
Simulation owns reality
The world is designed around sixteen interacting simulation systems: population, settlements, economy, food, politics, crime, culture, technology, religion, diplomacy, warfare, factions, migration, seasons, fate events, and legacy. The simulation runs on a fixed tick loop and is deterministic by construction — same input on the same shard at the same tick produces the same output, byte-for-byte, every time. The simulation is the only thing that decides what's true. Narrative is a read-only camera on top of it. AI translates events into prose; it never authors them. Hallucinations don't survive contact with the canonical event log. (Post on this.)
Stories emerge instead of being scripted
Picture the systems interacting over time. A drought stresses food production. Scarcity raises crime. Crime delegitimizes the leader. The leader's faction loses influence. A rival faction grows. Tension crosses a threshold and a schism fires. Rumors travel along trade routes to neighboring settlements. Diplomatic dispositions shift. Two settlements that were Friendly tip to Hostile and their trade route collapses. None of that gets written by hand. The narrative layer's job is to notice the moments worth noticing and surface them as story seeds: a noble house seeks allies after a succession crisis. Whether to engage is up to you.
NPCs aren't decoration
Every NPC has a personality (a vector of traits — risk tolerance, honor, aggression, religiosity, generosity, ambition), a family, a reputation, a relationship graph, and memory. NPC memory is designed in layers: episodic (specific events they witnessed), relationship (their history with each other character), reputation (what others say), emotional (how they encoded what they remember). Multiple NPCs witnessing the same event may form different memories of it — partial, mistaken, biased by faction loyalty or fear. A merchant's memory of a crime can drift. So can a guard's. Whose version becomes the public account depends on whose voice carries further.
The world has no chat box
Communication is designed to flow through a protocol called Skaldish. You type in plain modern English. The system extracts your communicative intent — greet, warn, persuade, threaten, spread rumor, declare loyalty — and renders it as in-world dialogue, in your character's voice, with your character's vocabulary. An arrogant noble says "I suppose I could assist you." An honorable warrior says "You have my word." A persuasive speech reaches an audience; a whisper reaches one ear; a rumor takes weeks to travel a region; letters are physically delivered. Players cannot reliably tell each other from NPCs. The chat box doesn't exist because chat would break the world.
Among the countless souls — the Skaldborn
Most souls are ordinary: they live, they die, they reincarnate, and the world remembers them the way the world remembers everyone. A rare few are Skaldborn — souls bound to one other across lifetimes. Across many lives, a Skaldborn pair may meet as allies, rivals, lovers, betrayers, destroyers, saviors. The relationship is the long narrative arc no single life resolves. It's the bone the rest of the architecture is built around.
What runs today, what doesn't
Skaldborn is in active development. Some of what's described above runs on the main branch right now; most is contract-and-design.
- Running today: the simulation substrate — the deterministic event envelope, the tick loop, the world's content manifest. The network gateway and browser client. The content pipeline. A byte-for-byte deterministic-replay test passes on every commit.
- Contract-and-design today: the sixteen simulation systems are spec'd, named, and contracted; their implementations are landing across upcoming development phases. The AI narrative service, the dialogue pipeline (Skaldish), the NPC memory pipeline, and the Skaldborn-pair destiny system are designed but not yet implemented on main. We deleted the previous implementations earlier this year because they failed an extensibility test, and we're rebuilding them under stricter rules.
The blog precedes the game. Read the dev journey.