Magic ingestion: import an existing manuscript in minutes

You have 80,000 words in Google Docs, Scrivener or a publisher PDF. Starting from zero in a new tool? Unthinkable. SagaScope magic ingestion takes your text and builds usable structure: detected chapters, created scenes, analyses started in the background.

That's the key differentiator vs « chat » AI: no need to re-paste 30 sheets every session. Pair with Word/Google Docs migration or Scrivener.

In brief

• Paste or drop DOCX, PDF, EPUB, TXT, MD, HTML.
• Mandatory preview before validation: check every segment.
• Import by act if the file is huge.
• Post-import: Codex → threads → timeline → committee.
• Ingestion structures; it doesn't fix narrative substance.

When to use it

• Import an existing manuscript (First draft or revised version)
• Restructure a long draft pasted as one block
• Migrate from another tool without manual retyping
• Resume an abandoned novel for coherence over 100,000 words

Step-by-step walkthrough

Step 1 — Prepare the source file

• DOCX / EPUB: most reliable formats for splitting
• PDF: OK if text is selectable; avoid badly OCR'd PDFs
• Pasted text: add explicit markers (Chapter 1, ## Act II) if auto-split fails

Step 2 — Launch ingestion

1. Structure panel → Magic ingestion
2. Paste text or drop a file
3. Wait for automatic chapter detection

Step 3 — Check the preview

The preview shows for each segment:

• Detected title
• Word count
• Opening lines excerpt
• Alerts (very short segment, possible duplicate)

Fix before validation: a part title detected as chapter creates false structure.

Step 4 — Validate and let it run

Validation → chapters and scenes created. AI analyses (entities, narrative threads, timeline) may continue in the background.

Common errors and fixes

Post-import path (7 days)

Limits by format

Common migration scenarios

From Scrivener: export as DOCX or compile to EPUB with explicit chapter titles. Scrivener folders don't map automatically — ingestion detects titles in text, not binder hierarchy. See the Scrivener migration guide.

From Google Docs / Word: use a consistent « Heading 1 » style per chapter before export. Avoid page breaks alone without titles: they don't create detectable chapters.

Manuscript already in SagaScope, new act added: re-import a block for a new act rather than re-merging everything — useful during major mid-book rewrites.

Existing novel + separate notes: import the manuscript first, then add notes to the Codex manually or via structured « document » scenes if you have them.

Where SagaScope fits

After import, you write in a tool that already knows your world: Codex, threads, timeline, graph. Ingestion is the entry point — not the end of work. Follow with style analysis and KDP prep as you approach publication.

Use case 1 — Scrivener migration, false chapter in preview

DOCX export from Scrivener: preview detects « Part II » as a chapter (80-word segment). You spot the alert before validation, merge with the next chapter after import. Without preview, you'd have a ghost chapter skewing numbering and narrative thread sparklines.

Use case 2 — Abandoned novel resumed after 6 months

You import 75,000 words written in Word, untouched since January. Day 1: structure validated. Days 2–3: Codex and threads populate. Day 4: thread consolidation — you recover three forgotten promises before rewriting act III. Ingestion replaced a linear re-read of 300 pages.

FAQ

Which formats are supported?

Pasted text, .docx, .pdf, .epub, .txt, .md, .html. The system detects chapter patterns (Chapter N, Act, markdown headings, etc.).

Can you fix the split before import?

Yes. A split preview shows segments, lengths and excerpts before final validation.

What happens after import?

Chapters and scenes are created; depending on mode, AI analyses (entities, threads, timeline) may continue in the background.

What if a false chapter is detected?

In the preview, spot segments that are too short or part titles. Merge manually after import or re-import by act with explicit chapter markers.

How long to analyze a large manuscript?

Structural import is fast. AI analyses (entities, threads, timeline) run in the background — expect several hours on 100,000+ words depending on load.

Conclusion

Magic ingestion removes the « I have to retype everything » barrier. Prepare a clean file, check the preview, validate — then let SagaScope build your novel's narrative memory. Real work starts after: consolidate narrative threads and resume writing with a tool that tracks your world.