creative-canon-lore · Last checked 2026-10-30
Series Bible Tracker: Keep Cut Plotlines Out of Your Next Draft
Rewrite a character in Draft 3 and your AI may still write the Draft 1 version. A simple living bible keeps cut plotlines from creeping back into scenes.
Quick answer
- Keep current canon, retired ideas and reveal gates in one living document
- Give every secret a chapter number so no character can know it early
- Tell your AI which draft is current at the start of every writing chat
Every long fiction project has the draft you cut and the draft you kept. The trouble starts when your AI collaborator remembers the wrong one.
Say you made a big retcon in Draft 3. In Draft 1, Commander Vance opened the Ashfall sluice gates for gold. In Draft 3, he was locked in the brig, and the quartermaster, Orin, forged the cipher. You ask a chat for the confrontation scene and it may write Vance as the traitor, because that is the version it saw.
Keep a living bible, not a pile of drafts
Drafts are for you. Your AI needs one short continuity page that says what is true now. Think of it as a template you copy for every book.
- Current canon. What happens in the book as it stands today.
- Retired ideas. The things you cut. Keep them, labeled as cut, so nobody rediscovers them and thinks they are new.
- Reveal gates. Who knows what, and from which chapter. Think of it as a knowledge log.
The reveal gate is the one writers forget
Kaelen does not learn about the forgery until Chapter 19. If your AI does not know that, it can let him mention it in Chapter 12, and the twist is gone.
Our rule: every secret gets a chapter number next to it.
Magic needs a price list
Hard magic works best when its costs stay consistent. In this series, holding a second-tier ward drops the caster's body temperature by 1.2 C per minute. Put that number in the bible and your AI cannot quietly let a character hold a ward for ten minutes.
You ask: Write the scene where Kaelen confronts Vance.
AI that read Draft 1: Kaelen storms in, furious that Vance opened the sluice gates for gold.
AI that knows Draft 3 is current: In Draft 3, Vance is locked in the brig and Orin forged the cipher. Kaelen does not learn that until Chapter 19, so here he blames Vance without proof.
Where the bible lives
Start each writing chat by pasting the current-canon page. If you work across several tools, a Knot project can hold it so each one reads the same page, and you can mark Draft 1 as cut when you rewrite.
Example bible page you can copy
| Entry | Current canon | Retired | Reveal gate |
|---|---|---|---|
| Siege of Ashfall, Year 412 | Vance was jailed two days before, and Orin forged the cipher | Vance opened the sluice gates for gold (Draft 1) | Forgery revealed in Chapter 19 |
| Vance's voice | Clipped and literal, no metaphors or contractions with subordinates | None | None |
| Ward magic | Holding a second-tier ward costs 1.2 C of core body temperature per minute | None | None |
The 4 rules in the starter checklist
- Draft 3 Canon Revision: Sluice Gate Sabotage Retcon. Draft 3 Governing Canon: Commander Vance was imprisoned in the Citadel brig two days before the Siege of Ashfall (Year 412); Quartermaster Orin forged Vance's cipher to open the eastern sluice gates. Kaelen believes Vance is guilty until Act II Chapter 19.
- POV Epistemic Firewall: Objective Truth vs Character Belief. Every series-bible entry must separate Objective World Truth from POV Character Knowledge with a chapter-unlock gate; no dialogue prior to Chapter 19 may treat Quartermaster Orin's forgery as known by Kaelen.
- Hard Magic Conservation Law: Aether Draw & Core Hypothermia. Casting any second-tier kinetic ward drops the caster's core body temperature by 1.2 C per minute of sustained hold; exceeding 3 minutes causes involuntary muscle rigor and slurred speech for 4 hours (no potion bypass exists).
- Dialogue Voice Invariant: Commander Vance Cadence & Lexicon. Commander Vance speaks in clipped declarative naval/engineering measurements, never uses metaphors or contractions when addressing subordinates, and refers to the Empire strictly as 'the Directorate.'
Test prompt
Check my Knot project 'Series Bible & Canon Continuity Tracker' for my governing Book 2 character canon, timeline invariants, and any replaced Draft 1 plot backstories. Then audit a new Chapter 14 dialogue scene where Commander Vance discusses the Siege of Ashfall with Kaelen: flag any reference that accidentally uses the replaced Draft 1 betrayal backstory and enforce the governing Draft 3 timeline.Frequently asked questions
Why do Claude and ChatGPT mix up old draft plotlines when I upload my series bible?
When a lore document or project folder contains both early outline notes and revised chapter notes, retrieval usually picks passages by how closely they match your request, not by which draft is current. Because Draft 1 and Draft 3 share the same character and place names, the model can blend both versions into one contradictory scene.
How do I track what a POV character knows versus what is objectively true in the world?
Separate every major plot secret into two fields: what is actually true in the world, and what each POV character knows and from which chapter. Avoid storing a plot twist as a flat character trait.
Should I delete old draft ideas when I rewrite a character backstory?
Do not delete them outright, because you often need to check which earlier chapters referenced the old backstory so you can patch them. Instead, mark the Draft 1 idea as retired by the Draft 3 rewrite so your AI is less likely to use it in new scenes while still helping you hunt down leftover continuity leaks.
Sources
- Retroactive continuity (reference): Definition of retcon
- Series bible (reference): What a series bible is
- Hard and soft magic systems (reference): Hard magic and consistent costs