What Loreon does not do.

What the checks do not catch

Loreon reads your prose against your canon. That framing sets a hard boundary: it can find a place where the manuscript disagrees with itself or with the bible, and it cannot find anything else.

• It cannot know your intent. A character who lies, an unreliable narrator, a contradiction planted on purpose for a later reveal — all three look identical to a clash caused by a mistake. You will dismiss findings, and that is the system working, not failing.
• It is only as good as your canon. A thin story bible gives the checks little to check against. Nothing here derives truth from nowhere.
• Off-page events are invisible. If two characters talked between chapters and you never wrote it, the check will flag the consequence as unexplained.
• Inference is not adjudicated. A character can reasonably deduce something nobody told them. Whether the leap is earned is a judgement call, and it is yours.

What still needs a human editor

Continuity is a floor, not a ceiling. A perfectly consistent novel can be a bad one, and nothing here will tell you so.

• Whether the story works. Validation reports structure, pacing and contradiction. Whether the ending is earned, whether the middle justifies its length, whether a reader will care — that is a developmental read, and a human's.
• Line editing, copyediting and proofreading. Loreon is not a grammar checker and does not enforce house style.
• Taste. No agent here will tell you a sentence is beautiful or that a character is boring.
• Sensitivity and accuracy beyond your canon. Checks read your book against your record of your world, not against the real one.

Where false positives come from

Every finding is a proposal, and some proposals are wrong. The recurring sources are worth naming so they do not surprise you: deliberate contradictions from lying or mistaken characters; setups in an early volume that pay off in a later one and read as dropped until they do; deliberately vague or non-linear chronology, where forcing a timeline finds conflicts that were never meant to resolve; and canon entries that are themselves out of date, where the finding is correct about a record that is wrong.

Findings cite their passages precisely so you can settle these quickly. Nothing is ever changed on the strength of a finding alone.

Size and format limits

• An imported file is capped at 10 MiB.
• An imported manuscript is capped at 150 chapters, 800 scenes and 50,000 paragraphs.
• Any single paragraph is capped at 64 KiB.
• Import accepts .docx, .md and .txt, or pasted text. A .docx is converted to text in your browser first.
• Export is Markdown, plain text and PDF. There is no EPUB export and no DOCX export, and no cloud-backup integrations.
• It is a web application. There is no offline mode and no desktop app.

What the agents will not do

• Edit your prose unasked. Checking agents read and report. Drafting agents run only when you ask them to.
• Run in the background. No check starts on its own. The margin stays empty until you ask.
• Spend credits without warning. Every run estimates its cost before you commit, at most the estimate is reserved, and your balance never goes below zero.
• Train on your writing. Your content is not used to train models — see privacy & ownership.

What we do not claim

We do not publish a hit rate. We have not measured what proportion of continuity errors Loreon catches on an arbitrary manuscript, so any number we printed would be marketing rather than measurement. What we will say is narrower and checkable: validation reads every chapter against canon, every finding cites the passages it is based on, and you can read the evidence yourself.

For what it does do, see what Loreon is and the continuity checker. For the method without any tool at all, the continuity checklist works with a spreadsheet and patience.