Session three: continuity, world, beta read
Before you start: Session two: voice checks and summaries
The draft is done, or a stretch of it is. This session finds what a careful reader would trip over, brings Cast & World up to date with what you actually wrote, and gets a first reader's reaction. Do them in this order: facts first, records second, feelings last. There's no point polishing the pacing of a chapter where the heroine is in two cities at once.
All three report first and save later. You'll be asked before anything goes into the book.
Continuity check
Run a continuity check on chapter 14.
The Continuity check skill reads the chapter and builds a fact sheet from your records: every character who appears or is mentioned, the places, groups and objects named, the lore rules, and the Blueprint scenes linked to the chapter with their timing. It then searches earlier chapters for the facts this one relies on ("the scar", "the silver mirror"), reading a whole earlier chapter only when a search isn't enough. It also looks at your comments, so it doesn't report what you've already marked.
What it looks for: physical details (eyes, scars, injuries that heal too fast), time and travel, people in two places, characters acting on news they haven't had yet, objects lost and then used, names that drift, and the text disagreeing with Cast & World, lore or the Blueprint. Style and pacing are left for the beta read. A dream, a lie or an unreliable narrator isn't an error; if the text gives no signal it's flagged as "check intent".
The report opens with one line saying what was checked against which sources, then a table: severity (High, Medium or Low), the issue, the quoted passage, what it conflicts with (also quoted), and a one-line fix. When either side could be right, you get both options: change the paragraph, or change the entry. It ends with the facts it couldn't verify. It never invents canon to settle a question.
Then you choose:
Leave comments for the High ones.
The entry is wrong, her eyes are blue. Fix the character entry.
The skill lists what it will add or change and waits for a yes. It won't rewrite your paragraph unless you ask.
For the whole book, say so ("all chapters") and expect it to take longer.
World bible sync
Drafting invents people and places faster than anyone updates the records. To catch up:
Sync my world bible with chapters 1 to 14.
The World bible sync skill loads your characters, places and lore first, then reads the chapters and collects every proper noun and coined term with where it appears. It searches the manuscript to count uses and find spelling variants. It may also look at your Spark boards, where an idea card might already describe a missing entry, and at pictures and maps, since a portrait can contradict the text about eye colour.
You get four lists:
- Missing: names with no entry, with first appearance, number of uses and every fact the text establishes, each quoted.
- Mismatched: entries the text contradicts, both sides quoted.
- Variants: "Aldren" in one chapter, "Aldrin" in another. It doesn't decide which is right.
- Unused: entries the chapters never mention. Listed only, since these are often for later.
One-off background names, like a waiter, are skipped unless you want everything, and the skill says what threshold it used.
It ends with the exact changes it would make. Proposed entries hold only facts from quoted passages; unknown fields stay empty. Say yes and it creates or updates the entries one batch at a time and reports what changed. Name exactly what you want: when we answered "Go ahead with the first two of those", it applied all three batches, including two record updates. Everything it did was in Activity and could be undone, which is why the next page exists. It never deletes an entry, never edits your manuscript, and doesn't set or remove pictures. If you'd rather review the proposal in the app, ask for it on a World bible Spark board instead.
Beta read
Beta read chapter 14. I care most about pacing and whether the ending pulls me on.
The Beta reader skill asks, if you haven't said, which chapter, what you want to know, and whether to read cold or with context. By default it reads with the book's overview, so it knows the genre it's reading as. With context it also reads the end of the previous chapter and the cast list, and the scene card if you ask whether the scene does its job.
What comes back:
- An overall impression, three to five sentences, as a reader.
- Reactions moment by moment, in reading order, each with a quote.
- Notes by area: opening, clarity, pacing, character, stakes, ending, and at least two passages that work and why.
- The top three things to look at, ranked by how much a reader would notice.
It reports reactions ("I lost track of who was speaking in paras 14 to 18"), not rules, and says when something is only taste. It doesn't rewrite sentences.
To keep the notes in the book, it offers a comment on each paragraph it discusses and a summary card on a Beta read Spark board. It shows you the comments first. This skill is told never to use the tools that edit chapter text.
Then revise
The findings are now comments in the margin, where you'll be working anyway. Fix things in the editor yourself, tick comments off as you go, and run the continuity check again on the chapters you changed.
If you do ask the tool to change your text ("fix paragraph 12 to say grey"), that's outside the skills, and the tool can edit the chapter directly. NovelOS takes a snapshot of the chapter first, and the change is in Activity, ready to undo.
Next: Review and undo AI changes
Checked against NovelOS Studio 1.5.1 · Updated · View as Markdown