Retcon vs continuity error

Every long story eventually collides with something it already said. What separates a retcon from a continuity error is not the size of the change or how far back it reaches; it is whether anyone meant it. That single difference decides how you should handle the contradiction, and whether readers will forgive it.

Two kinds of contradiction

A continuity error is an accident. Wikipedia defines the plot hole, its near relation, as "an inconsistency in a storyline that goes against the flow of logic established by the story's plot". The sword returns after it shattered; the character is in two cities on one day. Nobody chose it. Readers experience it as a mistake because it is one, and the fix is to repair the text until the story agrees with itself (see the seven continuity errors).

A retcon is a decision. Retroactive continuity, as Wikipedia defines it, is "a literary device in fiction" whereby established facts are later "adjusted, ignored, supplemented, or contradicted". The author knows what the story said and changes it anyway, on purpose. That intent is the entire difference between the two, and it is why the retcon belongs in a writer's toolbox while the continuity error belongs in the bug list.

The three classic retcon forms

The same article groups retroactive continuity into forms worth knowing by name, because each carries a different amount of reader risk:

1. Addition: new information that does not contradict the page. The mentor fought in a war nobody mentioned; the villain had a teacher. Nothing already written becomes false, so this is the cheapest form, and the one readers almost never resent.
2. Alteration: new information that contradicts and replaces the old. The character everyone watched die is alive; the accident was staged. Readers will notice, and the retcon owes them an in-story reason.
3. Subtraction: quietly acting as if a story, or part of one, never happened. The riskiest form, because the readers who loved the removed material are precisely the ones who remember it best.

So which one do you have

When you find a contradiction in your own draft, run it through a short decision procedure:

1. Is it intentional? A character lying, an unreliable narrator, a mystery you seeded on purpose: contradictions with intent are neither error nor retcon. Mark them intentional so revision, and any consistency checker, stops flagging them (see what is canon).
2. If it is accidental, is the earlier fact load-bearing? Ask what later scenes depend on it. If nothing does, and the new version serves the story better, you may promote the accident into a deliberate retcon. If the old fact is woven through the book, or the new version is just drift, fix the error instead.
3. Write down what you decided. A retcon is a decision with a paper trail: what changed, why, and how far the change reaches. An error is only a whoops. If you cannot say which one yours is, you have not decided yet.

How to retcon without losing readers

• Prefer addition over alteration, and alteration over subtraction. Take as little as possible; every established fact you unwrite is reader trust being spent.
• Give alteration an in-story mechanism. The death was staged, the memory was false, the report lied. A retcon the characters can discover and react to reads as story; a retcon only the author can see reads as vandalism.
• Prefer recontextualization to contradiction. The strongest retroactive changes leave every old scene exactly as written while changing what it meant, so the reader rereads old chapters with new eyes instead of discarding them. New information about an old scene beats a rewritten old scene.
• Record the decision and its reach. Note which chapters, facts and records the retcon touches, and update your story bible so future chapters follow the new canon instead of the old one you remember.
• In serials, consider acknowledging it. A book can quietly repair itself in its next printing; a published web chapter has already been read, and serial communities keep their own memory of what happened. An acknowledged change reads as an author making a call. A silent one gets discovered, and discoveries get argued about.

Not every contradiction is either

Keep the third category in mind. The lie a character tells, the narrator who does not know everything, the clue planted to pay off three books later: these are contradictions with intent behind them, and they are good craft. The practice is knowing which of the three you are looking at, because each has a different correct action: fix the error, record the retcon, or mark the intent and leave the text alone.

How Kanonara approaches this

Kanonara treats the distinction as a workflow. Apparent contradictions surface as Story Doctor alerts showing the evidence on both sides, and the author decides what each one is: fix it, mark it intentional so it stops being flagged, or accept the new fact and let it become canon from that approval on. Nothing is ever silently changed; a retcon in Kanonara is a decision you can see in the record. See how Kanonara works.