For LitRPG & progression authors
Ch. 4 — his mana pool was hard-capped at 40 until the Ascension.
Ch. 30 — he loosed a 120-mana firestorm without breaking a sweat.
Ch. 4 — his mana pool was hard-capped at 40 until the Ascension.
Ch. 30 — he burned all 40 and dropped — the firestorm guttering half-formed.
Your AI forgets chapter 4 the moment it writes chapter 30. The Narrative Graph remembers all of it — and flags the break while it’s still a draft.
why it matters
One detail breaks in chapter 30 — and the top comment isn’t about your cliffhanger. It’s about the mana that broke its cap.
The reader who caught it doesn’t write to tell you. They just stop turning up for the next chapter. That’s the slip that costs you.
see it side by side
Ch. 4 —Kael’s mana pool was hard-capped at 40 until the Ascension.
Ch. 30 — Kael loosed a 120-mana firestorm and barely felt the drain.
Ch. 4 —Kael’s mana pool was hard-capped at 40 until the Ascension.
Ch. 30 — Kael spent all 40 and collapsed, the firestorm guttering out — the Ascension was still chapters away.
how it works
Most AI writing tools carry the last two or three chapters forward as they write — a sliding window that forgets chapter 4 the moment chapter 30 is being written. The Narrative Graph builds a living map of your whole series — every character, fact, and rule — and checks each new chapter against all of it. Not the last few chapters. All of them.
Every character, fact, and rule across the whole series becomes a node in a living map.
The new chapter is checked against the whole graph — not just the last few chapters.
Each new chapter is checked for contradictions while you’re still reviewing it — before it reaches your readers. You decide on every flag; it’s your story.
They carry the last two or three chapters forward into each new generation. The contradiction back in chapter 4 is outside the window, so it slips through.
Every character, fact, and rule is held in a graph and each new chapter is checked against all of it. Chapter 4 is still in scope when you’re writing chapter 300.
a look at what you’re reserving
Chapter 30 · draft
The hollow shrieked down the tunnel. Kael raised both hands and channeled a 120-mana firestorm, and the dark caught fire.
flagged · continuity break (derived facts)
Reviewers disagree on this one — open it and decide for yourself. When they split, we widen the band and ask you; we don’t guess.
You decide on every flag. This is a catch to look at, not a grade.
Continuity break · derived facts
His mana broke its cap.
Canon · Chapter 4Mana Pool — 40 / 40. Hard cap until the Ascension. He cannot exceed it.
This chapter · Chapter 30Kael channeled 120 mana in a single cast.
We found a continuity break in Chapter 30 — Kael spent 120 mana on a 40 cap. Canon (Chapter 4) hard-caps him until the Ascension. Worth a look before this one reaches your readers.
You decide: revise · or tell us it’s intentional
what it replaces
Holding your canon straight isn’t free today. It’s just paid in time — and it still misses things.
Re-reading the whole series — 30, 100, 300 chapters — before you write the next one.
A story bible you update by hand, and forget to, right when it matters.
A beta readerwho finds the slip — after it’s already published.
$49/month, and the graph does it on every chapter — automatically, while the draft is still yours to change.
the indie plan
Everything you just saw, running on your whole series.
The Indie plan, the price, and exactly what’s included.
We use cookies to see which ads bring writers here — nothing else. You choose. How we use cookies.
Examples are illustrative, not real reader excerpts. We describe the free-tool sliding-window mechanism in plain terms so you can judge it yourself — no head-to-head score. (Mechanism reference: inkfluenceai.com, retrieved 2026-05-30.)