What the checks miss

PullAtlas has two kinds of checking. The continuity check is AI: it reads prose and judges it against your recorded canon. The name check and the placeholder inbox are plain string rules: deterministic, no AI, and exactly as clever as the rules on this page. Both kinds have edges, and it is better that you know them than discover them.

What a check reads

A continuity check is handed four things: your Atlas canon (every active entry with its summary, details, structured and custom fields, faction and rank, and connection labels), the cast’s recorded status as of the chapter being checked (keyed facts and states up to and including it, never later ones), the recorded relationships as of that chapter (kinds and verbs, including who knows about what), and the chapter’s own text. Very long chapters are truncated at roughly 40,000 characters, which is far beyond a normal chapter.

What it can catch

Contradictions between the chapter and what you recorded: a changed eye colour, an ability someone should not have, a character treated as alive after their recorded death, someone acting on knowledge the timeline says they have not learned, current rivals written as close allies. It also looks for contradictions inside the chapter itself: timeline math, who knows what, physical logic. Each finding quotes the exact phrase that triggered it, and when a finding reveals a change your timeline never recorded, it offers a one-click way to record it.

What it structurally misses

• Facts you never recorded. The check compares prose against your Atlas, not against some perfect memory of your story. If the scar changed shoulders and neither shoulder is written down anywhere, there is nothing to contradict. This is why capture is built to be a two-second gesture.
• Contradictions between two chapters’ prose. A check reads one chapter at a time against the recorded canon. If chapter three and chapter seventeen disagree about a detail that lives only in prose, no single check sees both sides.
• Intent. An unreliable narrator, a character who lies, deliberate misdirection: to the check these look like contradictions, because they are, on purpose. Dismiss the finding; dismissed findings stay dismissed on re-runs.
• Some real problems, some of the time. The check is a language model. It can miss a genuine contradiction and it can flag something defensible. That is why findings are worded as questions for you, each with its quote, and why nothing is ever changed without your click.
• Everything past the caps. A run reports at most 12 findings; a chapter with more needs a second run after the first batch is dealt with.

The rule-based passes

The name check flags capitalized words that sit one typing error away from an entity name or alias. The rules, in full: the word must start with a capital letter, must not be a recorded name or alias or a plain plural of one, must not be on a small list of common English words, and must be one edit (a swapped, added, dropped, or transposed letter) from a name of five or more letters, or one added letter from a four-letter name. Possessives are compared without the apostrophe-s. So it will catch Kestral and Restrel for Kestrel, and it will not catch a typo two letters deep, a lowercase name, or a misspelling that happens to be another real name. Anything it flags wrongly, you ignore once and it stays ignored for the project.

The placeholder inbox is even simpler: any single-line [bracketed] span in prose, up to 120 characters, is treated as a debt. It cannot tell a placeholder from prose that keeps literal brackets on purpose, which is why the inbox has a “not a placeholder” button that teaches it per project.

Why this page exists

Continuity tooling is easy to oversell, and manuscripts are not the place to find out a promise was marketing. A green pass here means: nothing contradicted what you have recorded, within the edges above. The more of your world you record, the more those edges recede; that is the deal, stated plainly.