Keep AI novel characters consistent
A worked continuity sheet, a chapter check and a revision example for long AI-written fiction. Keep facts separate from plans and summaries.
A long novel does not need to forget a character dramatically to lose a reader. A borrowed ring becomes a gift, an injured hand starts holding a sword, or a promised meeting quietly disappears. The prose can be fluent while the story is wrong.
The useful question before generating a chapter is: which earlier facts would make this scene impossible if ignored? Here is a small workflow you can use in any writing tool.
Keep facts separate from intentions
Imagine a courier carrying a sealed letter to a city council. The gate is closed until sunrise, but the letter must arrive before dawn. Those are established facts. “The gatekeeper becomes an ally” is a plan. Combining the two in one paragraph encourages a model to treat an intended friendship as something that already happened.
Keep three sections in your notes:
| Section | Example | What changes it |
|---|---|---|
| Established fact | The courier is outside the closed gate | An event in an accepted chapter |
| Current state | The letter is sealed and dry in an oilskin pouch | A later event or an author correction |
| Intended direction | The gatekeeper may become an ally | Your decision about the arc |
Give important facts a chapter reference. “Letter deadline: before dawn, chapter 1” is easier to audit than a vague memory of an urgent delivery. Keep unresolved questions separate: you have not yet decided what is inside the letter.
Supply the facts this scene depends on
A good next prompt can be short: “The courier searches for another way into the city. Keep the letter sealed. The council must receive it before dawn. The gatekeeper has not agreed to help.”
This does not require pasting the entire story into every instruction. In webnovellm, recent chapters travel in full, older ones become summaries, and the writer can search previous chapters and fetch story-bible entries. That supplies context; it does not guarantee the model will interpret every detail correctly. Read the draft before accepting it.
Check four things before accepting
- Identity: did the person keep the same relationships, motivations and knowledge?
- State: are injuries, locations, possessions and promises still correct?
- Rules: did the world or power system suddenly allow something previously impossible?
- Time: can these events fit between the previous scene and the deadline?
For the courier, a draft in which the council opens the letter at noon has missed the point even if every sentence reads well. A draft in which the gatekeeper hands over a spare key also needs scrutiny: did the scene earn that change, or merely skip the obstacle?
Revise the contradiction, then check its consequences
Use a precise revision request: “The courier is still outside the gate. Remove the paragraph where the council reads the letter. Have the courier find a drain entrance, but keep the letter sealed and the deadline before dawn.”
Then reread the scene. Removing one contradiction can leave another: the courier may mention knowing the contents of a letter that has never been opened. Look at the causal chain, not just the corrected noun.
If you edit an accepted chapter in the app, its summary is rewritten. Check related bible facts too, especially if you changed an earlier event rather than just its phrasing. A summary and a fact sheet have different jobs, and neither replaces your final judgment.
Try the sample walkthrough, then read how memory works and how to plan a cultivation arc.