Most AI worldbuilding tools are pitched as generators. You describe something, they produce it. The assumption is that you are starting from nothing.
The more useful case — especially in a long-running campaign — is the opposite. You already have the material. Something changed. And you need the entry to reflect that change without rewriting the whole thing yourself.
The Oracle works both ways. Hand it an existing entry with a specific instruction, and it revises rather than generates. You stay in the director's chair. It handles the rewrite. You review the draft and decide what lands.
When revision matters more than generation
Generation is useful at the start of a campaign, when you are building from scratch. Revision is useful from session five onward, when your world has history and the history keeps changing.
Some examples of when you would reach for revision over generation:
- An NPC whose allegiance shifted after a player decision
- A faction whose power structure collapsed following an arc
- A location that was partially destroyed, occupied, or transformed
- An entity whose secret was revealed to the players — the entry can now be written from the perspective of someone who knows, so that subsequent summaries or handouts generated by the Oracle reflect what the players now know rather than what the NPC was trying to hide
- A character whose motivation made sense early in the campaign but needs updating to reflect what they have been through
In each case, the existing entry is mostly right. Something specific changed. You do not want to start over. You want a targeted update.
How to direct a revision
The key is specificity. The more precisely you describe what changed and what to keep, the better the draft.
Good revision prompts usually include three things:
- What changed
- What must stay the same
- What tone or perspective the entry should now use
Vague:
Rewrite this NPC.
Specific:
The players exposed Mira as a resistance informant in session 22. Update her entry to reflect that her cover is blown, her motivation has shifted from survival to active defiance, and she is now operating openly. Keep her voice and her established relationships with the dockworkers' guild.
The Oracle reads the existing entry alongside your instruction and produces a revision as a draft. The original stays intact. You compare, accept the parts that work, edit what does not, and discard anything that missed. The principle that drafts are not canon applies here too — nothing replaces the existing entry until you decide it should.
Quick revision commands:
- "Add a flaw. Keep everything else."
- "This faction description is accurate but the tone is too neutral — rewrite it as if the narrator is afraid of them."
- "The players destroyed the iron bridge in session 18. Update this location's description accordingly."
- "This character now knows the truth about the Covenant. Rewrite from that perspective."
- "The scope of this faction's influence has grown since this was written. Expand the reach section without changing the core motivation."
What stays yours
Directing a revision is not the same as delegating the entry. You are specifying what changes and what does not. You are setting the constraints. The Oracle executes within them.
After the draft comes back, you are still the one deciding whether the updated tone feels right, whether the new motivation is consistent with everything else you know about this character, and whether the revision creates any unintended inconsistencies elsewhere in the vault.
That judgement does not transfer. The Oracle can help check against the vault, but it cannot replace your judgement about tone, intent, and what matters most at the table.
Review is not optional. It is the part where authorship happens.
Revision as a campaign habit
The longer a campaign runs, the more your vault accumulates entries that were accurate when they were written and are now partially out of date.
Using revision as a regular habit — after major arcs, after session events that change established facts, after player decisions that shift relationships — keeps the archive reflective of the actual current state of your world rather than the state it was in six months ago.
Because the vault is local-first, you can experiment freely: radical structural rewrites, tonal shifts, speculative changes to see how they feel — without server latency, data tracking, or cloud storage limits. Nothing leaves your machine until you decide it should.
The Oracle handles the mechanical rewrite. You handle the judgement. The vault stays honest.