I Wrote 25 Chapters With Zero Contradictions: Here's How

This is an illustrative walkthrough of the kind of test we run, not a published study. The book, the chapter numbers and the examples below show what to look for, not results you should expect.

Every writing tool says it keeps your story straight. The only way to know is to test it on a book built to break it. This post walks through how that kind of test is set up, what to check at each stage, and what the Consistency Engine does when a chapter gets something wrong.

The Test Setup

Say the test book is a 25-chapter fantasy thriller designed to be hard. A setup like this one stresses every part of a consistency system:

• 8 named characters with detailed physical descriptions, personality traits, and relationships
• 1 character death in chapter 6 -- a deliberate trap to see whether a language model brings them back
• 3 concurrent timelines -- present day, flashbacks, and a parallel storyline
• A magic system with strict rules -- elemental affinity, no healing magic, verbal incantations required
• 4 political factions with alliances that shift mid-story
• Character relationship changes -- allies becoming enemies, a betrayal, a romance subplot

This is the kind of complexity that trips up a tool relying on a chat's memory alone. As we explain in why every AI tool contradicts itself after chapter 10, a long book soon outgrows what a model is shown at once, and early details are the first to slip.

What to Check: Chapter by Chapter

Chapters 1-5: Setup Phase

The first five chapters establish the world, introduce the cast and open the three timelines. This is where the Story Bible fills up: after each chapter is drafted, the system proposes the facts it found (descriptions, relationships, world rules, places) for you to review.

What to check here: have you written or confirmed the facts you care most about? A fact you wrote or confirmed is one a later chapter is held to. A fact the system inferred and you never confirmed is treated more gently: a chapter that disagrees with it comes back with a note asking which is right.

Most tools look fine at this stage. The real test comes later.

Chapters 6-10: The First Stress Test

Chapter 6 is the death. Once it is drafted, open the Story Bible: is the death recorded, with the chapter it happened in? Confirm it. From then on, the check before drafting warns you if the plan puts that character in a present-day scene, and after drafting, a chapter that brings them back is repaired or held.

Chapter 8 is the trap inside the trap: a flashback, set before the death, that features the dead character. The result to hope for is a chapter where they appear in the flashback and stay dead in the present. If a check flags the flashback anyway, read the note; if the chapter is right, keep it as written.

Chapters 11-15: Alliance Shifts

Say the alliance between two factions breaks in chapter 12. That one change ripples: alliance status, character attitudes, faction dynamics, which places are safe. What to check in chapters 13 to 15: does anyone still talk about "our allies" when they should not?

This is where most tools struggle, because one event updates a cascade of facts. Relationship and attitude drift is often a judgment call, so expect it to come back as a note quoting the line rather than a hold. If the Story Bible has not picked up the new state, update it yourself, so later chapters are drafted with it.

Chapters 16-20: Peak Complexity

By chapter 16 the Story Bible holds a lot of facts, all three timelines are active, and the magic system has been used in many scenes.

A hard case to set up here: four characters from different factions meet at a place that was destroyed in chapter 14. A good result is a chapter that has them meet in the ruins, or a check that flags the scene so you can decide. A bad result is an intact hall that nobody remarks on, and no flag at all. Write down which one you get.

Chapters 21-25: Resolution

The final five chapters reveal the betrayal, converge the timelines and lean hardest on the magic rules set in chapter 3. Read the climax against those rules line by line: if healing magic is forbidden, does anyone get healed? A model under pressure to resolve a plot reaches for the easiest fix, which is why the ending is where a test like this earns its keep.

What Logic-Locking Is Meant to Catch

A clean finished chapter does not mean the first draft was clean. The useful thing to log in a test like this is what the checks caught along the way, sorted by kind. In a run of this shape, these are the kinds to look for:

• A dead character in a present-tense scene. If you wrote or confirmed the death, the chapter is repaired or redrafted, and held for you if it is still wrong.
• Small physical description variations. An eye colour or a scar that disagrees with a trait you wrote is repaired in place or redrafted. A line where light or magic changes how the eyes look comes back as a note, not a fix.
• A broken magic rule. Healing magic in a world that forbids it, when that rule is one you set, is treated like a contradicted fact.

What happens next depends on the kind. A contradiction of a fact you wrote or confirmed is repaired in place or the chapter is redrafted, up to 2 times, and if it is still there the chapter is held for you. A judgment call, or a fact the system inferred that you never confirmed, comes back as a note that quotes the line. Log both: the holds show what the checks stopped, and the notes show where your own reading is still needed.

What This Means for Writers

A 25-chapter book at this level of complexity is ordinary for indie authors and genre fiction writers, so it is a fair size to test on. The point of this walkthrough is not a score. It is a checklist you can run on your own pages: plant a death, break an alliance, destroy a place, forbid a kind of magic, then read chapters 10, 15 and 20 against the Story Bible. What the checks do today is described in the 9 checks.

What changes is where your time goes. You still read every chapter. You stop re-reading every earlier chapter before drafting the next one, because the Story Bible keeps the facts and the checks run after each draft. Confirming the facts that matter to you is the part only you can do.

Try it on your own book: a new account gets 3 free chapters, no credit card required. Draft a few chapters, watch the Story Bible fill in, confirm what matters, and read what the checks say. Want to learn more? Read our complete guide to AI story consistency, see how Novarrium stacks up in our best AI writing tools for novels comparison, or read how other tools handle a long book.