Your Campaign Knows More Than You Remember

Is Captain Voss still alive? When did the Ironclad Guild collapse, exactly? Was it before or after the party visited Thornhaven? And that plot thread from Session 3, the one where the merchant mentioned a shipment that never arrived, did anyone ever follow up on that?

You're sitting at your prep desk, and you can't answer any of these questions without opening four different documents, scanning through session notes you wrote at midnight, and hoping past-you was thorough enough to label things clearly. Past-you was not.

This is the problem. Not encounter balance, not NPC generation, not map design. Those have solutions. The problem that quietly ruins campaigns is memory. Yours is fallible. Your players' is not.

They remember that Voss had a scar on his left hand. They remember the name of the innkeeper's daughter from Session 2. They remember the exact wording of the prophecy you improvised during a bathroom break and immediately forgot. Your campaign generates information faster than you can organize it, and every session widens the gap between what exists in your world and what you can actually access when you need it.

We built three features to close that gap. Not as separate tools bolted onto a dashboard, but as a connected pipeline: one that watches your campaign's health, one that organizes everything your campaign knows, and one that shows you how it all moves through time.

The Check Engine Light

The Health Dashboard is the simplest of the three, and the one you'll glance at most often.

Six cards. Entity count, fact count, contradictions, extraction queue, sessions tracked, last content update. Green means fine. Amber means something's drifting. Red means you've got a hard contradiction that needs resolving before your next session.

The metaphor isn't accidental. You don't read your car's repair manual every time you drive to the store. You glance at the dashboard. If everything's green, you drive. If something's amber, you make a mental note. If something's red, you pull over.

Campaign prep works the same way. Most weeks, you don't need to audit your entire world. You need to know if anything broke since last session. Did the extraction catch a contradiction between what you said about Voss in Session 4 and what you said in Session 11? Did a fact extraction job fail, leaving a gap in your records? Has it been three weeks since you added new content, which might mean a whole arc of play hasn't been captured yet?

The Health Dashboard answers those questions in two seconds. No digging. No scanning through notes. Just a strip of signals at the top of your campaign page that tells you where to focus your attention.

The Repair Manual

If the dashboard tells you something's wrong, the Campaign Bible tells you what and where.

Think of it as a living reference document for your entire campaign. Every entity (NPCs, factions, locations, items) gets an entry with its facts, relationships, contradictions, and status. Not a narrative summary you wrote once and forgot to update. A structured record that grows as your campaign grows, because it's built from the facts your sessions actually produce.

Captain Voss has an entry. His status says "active." His facts include his rank, his scar, his grudge against the Ironclad Guild, and the deal he made with the party in Session 7. His relationships link him to the Guild (former member), to Thornhaven (stationed there), and to the party's cleric (owes a debt). If you told your players in Session 4 that Voss lost his rank and then accidentally referred to him as "Captain" again in Session 11, the Bible flags the contradiction. Hard contradictions get red markers. You decide which version is canon.

The part that changed our own prep the most: every entity gets an AI-generated hook phrase. A single compressed line designed for improv. Something like "Voss: bitter loyalist, testing whether the party deserves his trust." It's not a backstory. It's a lens. When a player walks up to Voss unexpectedly and you need to be him in three seconds, the hook phrase gives you a voice without requiring you to reread four paragraphs of notes.

The Bible organizes entities into sections (cast, factions, locations, items, lore) with cross-references between them. Click on the Ironclad Guild and you see every NPC connected to it, every location where it operated, every session where it came up. The information was always there, scattered across your notes. The Bible just makes it findable.

The Evolution View

The Campaign Bible shows you what your world is. The Living World Timeline shows you what your world was, and where it's going.

It's a swimlane grid. Each entity gets a horizontal lane. Sessions run along the top as columns. Events appear as cards positioned where they happened: "Ironclad Guild founded" in Session 0 (backstory), "Guild hall burned" in Session 6, "Voss defects from Guild" in Session 8, "Guild remnants resurface in Thornhaven" in Session 14.

Lay those lanes side by side and something happens that session notes can't give you. You see parallel arcs. Voss's personal story and the Guild's organizational collapse aren't two separate narratives. They're interleaved. The Guild collapses because Voss defects. The Thornhaven resurgence happens because the remnants need a new base. Cause and effect become visible.

Three specific things the timeline reveals that flat notes never will:

Stale threads. If an entity's lane goes quiet for five sessions, something dropped. Maybe intentionally, maybe not. The timeline's gap analysis catches these and suggests where a missing event might belong. That merchant shipment from Session 3? If nobody's touched it since, the timeline flags the gap. You decide whether to let it fade or weave it back in.

Status jumps. Voss goes from "active" in Session 4 to "deceased" in Session 12 with nothing in between. The timeline catches the jump and suggests a midpoint event. What happened in Sessions 5 through 11 that led to his death? If you know, you can fill in the gap with one click. If you don't, that's a story you haven't told yet, and now you know it needs telling.

Causal chains. The timeline can trace connections between events across lanes. The artifact stolen in Session 2 leads to the faction war in Session 8, which leads to Voss's death in Session 12. These chains get AI-generated narrative summaries so you can see the through-line of your campaign's major arcs without reconstructing them from memory.

Why These Three Together

Any one of these features is useful on its own. A health dashboard is a nice quality-of-life improvement. A campaign bible is a reference tool. A timeline is a visualization.

Together, they're something different. They're a feedback loop.

The Health Dashboard tells you the campaign needs attention. The Campaign Bible shows you exactly what's inconsistent, incomplete, or contradictory. The Living World Timeline shows you when things went wrong and what threads need reconnecting. You move from signal to diagnosis to understanding without switching contexts, without opening a different app, without trying to reconstruct your campaign's history from scattered documents and fading memory.

We built these because we needed them. Not as product managers looking at a feature matrix, but as GMs who kept getting caught by our own players. The cleric who remembered a promise we made in Session 2. The rogue who asked about an NPC we'd accidentally killed off-screen. The entire table that noticed we'd contradicted ourselves about the timeline of a war.

Your players aren't trying to catch you. They're engaged. They're paying attention. They remember because they care. The least you can do is care back, and caring means knowing your own world well enough to reward their attention instead of fumbling through notes while they wait.

How Much of Your Campaign Are You Actually Tracking?

Here's a question worth sitting with. After ten sessions, a typical campaign has generated dozens of named characters, multiple faction dynamics, a handful of unresolved plot threads, and at least a few contradictions nobody's noticed yet. How much of that is written down? How much of what's written down is organized? How much of what's organized is accessible when you need it, at the table, in the moment, with four players looking at you?

If the honest answer makes you uncomfortable, you're not alone. That discomfort is the whole reason this pipeline exists.

Your campaign already knows more than you remember. Now you have a way to ask it.