A continuity engine for the whole book.

PlotWalker is not enabled in the beta you can download today, and nothing on this page is something you can open yet. I am writing it down anyway, because it is the reason Draftline exists and because the principles it is built on are ones you can judge now.

In development

What goes wrong at seventy thousand words

You gave a character gray eyes in chapter four and green ones in chapter nineteen, because the second description was written eight months after the first. A lieutenant mentions the transponder in chapter seven, although nobody tells him about it until chapter nine. Somewhere in act two a subplot goes quiet, and the only way to find out where is to reread forty thousand words with a notepad. None of these are hard to fix once you know about them, and every one of them is easy to miss until a beta reader writes in the margin.

What PlotWalker is being built to do

PlotWalker reads the manuscript and keeps a record of what each sentence establishes: who is where, who holds what, who knows what and when they learned it, and what the clock says. When two passages disagree, you get a question with both sentences attached and a button to jump to either, and you decide whether it is an error or a deliberate device. You will also be able to ask the book a plain question, such as where an object first appeared or what a character has told anyone, and get an answer assembled from your own sentences with each line linked to its source. Dreams, flashbacks, and simulations are tracked as separate realities, so a contradiction between a dream and the waking story is reported as a device rather than a mistake.

Rules it is built under

These are design decisions, and they are the part of PlotWalker that already exists in a form you can hold me to. Every finding will point at the exact sentences that produced it. Where the text is ambiguous the engine will stay silent rather than guess, and where two passages disagree it will keep both accounts instead of averaging them into one. All of it runs on your machine, with no model making judgments about your book and no network call, so the analysis stays as private as the manuscript.

Evidence-linked — every conclusion carries the sentence and the chapter that produced it
Never invents a fact — it repeats what your sentences say and composes nothing
Abstains when unsure — an ambiguous pronoun stays unassigned rather than being pinned on the nearest name
Keeps conflicting accounts — what a character claims and what the narrator says are two records
Runs locally — deterministic processing over your own sentences, with nothing sent anywhere

The parts that ship now

The foundation PlotWalker is built on is already in the app. The Characters Codex detects the cast from the manuscript and maps every character across every chapter, which is the roster the continuity work depends on. Chapter history keeps deduplicated snapshots of each chapter as you edit, so when a continuity slip is finally traced to a revision, the revision is still there to look at. The rest of this page arrives when it is ready, and the download page will say so.