Consistency and research

Two tools that both write into — and read from — the story codex.

The consistency check

At the bottom of the codex: ✦ Check N chapters · ≈X cr.

One call reads your written chapters against your pinned canon and returns specific, factual contradictions. Not style notes, not opinions about the plot — things that cannot both be true.

Each result is a card carrying:

• a severity — contradiction or warning
• the chapter it is in
• the exact quote that conflicts
• what the issue is, and a suggested fix

Click a card to jump straight to that chapter.

A clean audit returns nothing, which is the answer you want.

It audits against the codex. A contradiction between two chapters that you never pinned as canon may not be caught — the codex is what tells the audit which facts are supposed to hold.

Deep research

For books that have to be right about the real world.

Give a topic. Manuscript Studio then:

1. Plans a set of searchable questions from your topic and premise.
2. Searches the live web for each one.
3. Synthesises what it found into codex entries, each carrying the sources it actually came from.

The citations are read from the pages the model genuinely fetched, so it cannot invent a source. Findings appear with clickable source chips and become part of your canon.

Cost and plan

A flat 10 credits, refunded in full if the job fails. It is a fixed price because the work is bounded — you always know what you are spending before you start.

Paid plans only.

It runs in the background

Research is a worker job. Close the tab, come back, and it is either still running or done. The codex refreshes when it finishes, and an in-flight job is picked back up when you reopen the panel.

What to watch for

• Autosave pauses for a book being researched, so the worker's writes are not clobbered by your editor. It resumes when the job ends.
• Research entries are findings, not gospel. They carry their sources so you can check them, which is the point — click through before you build a plot on one.
• Run the consistency check before you export, not after. It is the cheapest proofread in the product and it catches the errors readers actually notice.