Canon Enforcement — Never Break Your Own Story Rules

AI cross-references every scene against your established canon. Character details, timeline, geography, world rules — automatically checked across your entire manuscript.

0
K+ Words Supported
0
Canon Categories
0
Competitors With This

Ready to write with real quality feedback?

Try ProseEngine Free

The Problem Every Novelist Faces

The longer your manuscript, the more details you establish — and the more likely you are to contradict yourself. Readers notice. Reviewers notice. And by the time you catch it in editing, the fix cascades across dozens of scenes.

👁

Character Detail Drift

Blue eyes in chapter 3, green eyes in chapter 27. A scar on the left hand that migrates to the right. A backstory detail that quietly changes. These small errors destroy reader trust.

Timeline Contradictions

A character references “three years ago” in scene 40, but the event happened five years before in scene 12. Timelines are the most common source of continuity errors in long fiction.

💠

Dead Characters Reappearing

A character dies in Act 2 but is casually mentioned as alive in Act 3. A destroyed location is described as intact. World-state changes that your prose forgets about.

🌍

Geography and Distance Errors

Characters traveling between cities in hours when you established the journey takes days. Rooms described with different layouts. Maps that contradict your prose.

Magic and Technology Rule Breaks

Your magic system has rules — until a scene where the protagonist conveniently breaks them without explanation. Technology that works differently depending on the plot's needs.

👥

Relationship Inconsistencies

Characters who are enemies in one chapter and allies in the next with no transition. Family relationships that change. Power dynamics that shift without narrative justification.

How Canon Enforcement Works

Canon enforcement isn't a grammar tool or a generic AI feature. It's a purpose-built system that cross-references every scene in your manuscript against the canon you've established in your Story Codex.

1

Build Your Story Codex

Create entries for characters, locations, items, factions, events, and concepts. Define the details that matter — physical descriptions, timelines, relationships, rules, and world-state changes.

2

Write Your Scenes

Write naturally. Don't worry about checking every detail against your notes. Canon enforcement runs in the background, cross-referencing each scene against your established codex entries.

3

Review Flagged Violations

Canon enforcement flags specific contradictions with exact references — what was established, where it was established, and how the current scene conflicts. Fix violations before they compound.

ProseEngine Story Codex character profile showing scene mentions and character progressions

What Canon Enforcement Catches

Real examples of the kinds of contradictions that slip past human review but get flagged automatically by canon enforcement.

⚠ Character Detail Violation

Eye color changed from blue to brown

Elena's eyes are described as “deep brown” in this scene, but her Story Codex entry establishes blue eyes, confirmed in scenes 3, 7, and 14.

Scene 31, paragraph 4 · Codex: Elena Vassos → Physical → Eyes
⚠ Timeline Inconsistency

War referenced as 10 years ago — codex says 7

Marcus tells the council the war ended “a decade ago,” but the Story Codex timeline places the armistice 7 years before the current story year.

Scene 45, dialogue line 12 · Codex: Events → The Armistice → Year
⚠ World Rule Violation

Character uses psionic ability after established burnout

Nira uses telepathy in this scene, but Scene 38 established that she entered psionic burnout (minimum 72-hour recovery per codex rules). Only 18 hours have passed in story time.

Scene 41, paragraph 9 · Codex: Concepts → Psionic Burnout → Recovery Time
⚠ Geography Error

Travel time contradicts established distance

The squad reaches Outpost Seven in “under an hour” on foot, but the codex establishes the outpost as 40 kilometers from base camp. Previous scenes showed the journey taking a full day.

Scene 52, paragraph 2 · Codex: Locations → Outpost Seven → Distance from Base
⚠ Relationship Conflict

Character references a relationship that hasn't been established yet

Jax calls Commander Sorell “old friend” in dialogue, but their codex relationship is “subordinate/superior — hostile.” No scene between them shows a friendship developing.

Scene 28, dialogue line 3 · Codex: Jax Navarro → Relationships → Commander Sorell

The Canon Audit Report

Run a full-book canon audit to scan every scene in your manuscript at once. The audit report gives you a complete picture of your novel's internal consistency.

Sample Canon Audit Summary

Scenes Scanned 127
Canon Entries Referenced 48
Scenes Passing Canon Check 119
Scenes With Violations 8
Total Violations Found 14
Character Detail Violations 5
Timeline Inconsistencies 4
World Rule Violations 3
Geography / Relationship Errors 2
Canon Compliance Score 93.7%
📋

Violation-by-Violation Breakdown

Every violation is listed with the exact scene, paragraph, codex entry, and explanation. Click any violation to jump directly to the conflicting passage in your editor.

🔄

Re-Audit After Fixes

Fix the flagged violations, then re-run the audit. Watch your compliance score climb toward 100%. The audit history shows your manuscript's consistency improving over time.

Works Across 500K+ Words

Canon enforcement was built for the scale of real fiction projects. Whether you're writing a standalone novel or a multi-book epic fantasy series, your canon stays consistent.

📚

Series-Wide Consistency

Your Story Codex persists across all books in a series. Canon established in Book 1 is automatically enforced in Book 2, Book 3, and beyond. No more spreadsheet archaeology.

💾

Codex Grows With Your Story

As you write, your codex grows. New characters, locations, and rules are added. Canon enforcement adapts in real time — every new entry becomes part of the consistency check.

🔧

No Competitor Offers This

Other writing tools have character databases. None of them cross-reference those databases against your actual prose to catch contradictions. Canon enforcement is unique to ProseEngine.

Frequently Asked Questions

What kinds of contradictions does canon enforcement catch?

Canon enforcement catches character detail changes (eye color, age, background), timeline inconsistencies (events in wrong order or impossible timeframes), geography errors (characters teleporting between locations), magic/technology rule violations, relationship contradictions, and any detail that conflicts with what you established earlier in the manuscript.

How does canon enforcement work with the Story Codex?

Canon enforcement cross-references every scene against your Story Codex — the database of characters, locations, items, factions, and world rules you've built. When a scene contradicts an established codex entry, it flags the specific conflict with the exact detail that was violated.

Can canon enforcement handle a 500,000-word series?

Yes. Canon enforcement is designed for long-form fiction including multi-book series. Your Story Codex persists across all books in a series, so canon rules established in Book 1 are automatically enforced in Book 5.

Is canon enforcement available on all tiers?

Canon enforcement is available on Author and Studio tiers. The Story Codex itself is available on all tiers including Free. All paid tiers include a 14-day free trial.

Your Story Has Rules. Enforce Them.

Stop catching contradictions in reviews. Start catching them as you write.

Try Canon Enforcement Free

Explore More Features

Quality Scoring AI Audiobook Novel Generator Drift Detection Quality Gate Author Packs Engagement Boost Story Codex Scene Finder Scene & Canon Audit Story Charts Version Diff