Use cases · Series authors
Book one is canon now.
You are starting book two, and book one is no longer a draft you can quietly revise — it is fixed canon a reader has already read. Every name, rule, and rank you set down has to hold. The threads you planted have to either pay off or stay visibly owed, not vanish. And somewhere in a hundred thousand words of book two, a fact from book one is going to want to drift — a rank that quietly changes, a courier who becomes a clerk — and the only reader positioned to catch it read book one closely enough to remember. Loreon is built to be that second reader: one project holding every volume's canon, and a check that reads the books against each other so book three still agrees with book one.
The pains
What a series does to continuity.
A single novel already strains memory. A series multiplies it across books that can't be revised once readers have them. Three failures recur:
- Locked prior-volume canon. Book two can't contradict book one — but book one's facts live in your memory and a pile of notes, not anywhere book two gets checked against.
- Cross-volume threads. A setup planted volumes ago has to be tracked all the way to its payoff, or flagged as still owed — not quietly forgotten.
- A fact that must stay identical across books. A name, a rule, a rank, a date — it has to agree with itself across hundreds of thousands of words, in a document you wrote years before the one you're writing now.
The mechanisms that serve you
One canon, checked across volumes.
Loreon holds a series as one project with many volumes sharing one structured canon — a character's rank, a substance's rules, a faction's reach are one reference every volume writes against, not a new bible per book. When you ask, an on-demand cross-volume coherence check reads the volumes against each other and reports where a later volume drifts from an earlier one, or where a planted thread is still owed — it finds and cites, it does not edit, and it never runs behind your back. For the scene in front of you right now, the same consistency check reads that scene against canon whenever you ask.
- Findings, not fixes. A cross-volume finding cites both volumes and passages; resolving or dismissing it stays yours to do. The planning method, tool aside, is in how to plan a book series.
- Run it before a volume locks. Check book one's canon before it locks, then check again as book two grows — maintaining continuity walks through the discipline the check automates.
Carries a sealed letter through Volume I and keeps it unopened — a thread the series still owes a payoff.
A thread tracked by state — planted, carried, due — is what a cross-volume coherence check reads for.
Common questions
Series, specifically.
Do I make one project per book?
No — one project, many volumes, one shared canon. That is what lets book two write against everything book one established, instead of starting from a blank bible.
How does it catch a book-two contradiction of book one?
The on-demand cross-volume coherence check reads the volumes against each other. Findings cite the volumes and passages involved — a rank, a name, a rule that moved between books — and you resolve or dismiss each one; the check never edits your prose for you.
What does it cost?
Prepaid credits at one cent each — no subscription. The editor is free, and every agent run, including a coherence check, shows its estimated cost before you commit. See pricing for the packs and what's free.
Loreon · The Writing Studio
Start book two on canon that holds.
The editor is free, and welcome credits cover your first real agent work — no subscription, no card on file.