Liminalis
Lens 01 novel
Forseries planners · mid-draft novelists · co-writing pairs
Novel lens

“I've written ninety thousand words and I've lost the thread.”

The Novel lens is for the part of long fiction that isn't sentence-writing: knowing what you've already established, which threads are still live, whose arc turns where, and what you set up in book one that nothing has ever paid off.

§ 01  The weave board

“Which thread am I dropping, and where?”

Plot threads and character arcs become spines. Beats are placed on a book × chapter grid. A thread that quietly dies after chapter eleven stops being a nagging feeling and becomes a row with nothing in it.

Weave board — The Cartographer's Debt (series) 3 books · 6 spines · 24 beats
Spine Book I — The Cartographer's Debt Book II — The Longer Road Book III
ch 1–4 ch 5–8 ch 9–12 ch 13–16 ch 1–6 ch 7–12 ch 13–18 ch 1–8 ch 9–14
The compassthread · main setup turn turn turn pay
Wren — want / liecharacter arc ghost t1 t2 t3 break need
Marisol's ledgerthread · secondary setup turn turn pay
The amber hallthread · motif setup turn
Corvin — the ghostcharacter arc ghost t1 t2 t3 need
The guild collapsethread · world setup turn turn turn turn pay turn pay
The weave board. Rows are thread spines and character arcs; columns are books and chapter ranges. The highlighted row is the finding: the amber hall has a setup and a turn in book one and then nothing at all — a motif introduced and abandoned. Representative composite of the application UI.
§ 02 staged generation
Ruleeach stage is generated against everything already decided
§ 02  Planning

A build order, not a blank page.

Planning a series is a dependency graph pretending to be a document. Liminalis makes the dependencies explicit: every stage is generated against everything decided before it, and you edit each one before the next runs. Nothing is committed silently — stages arrive as drafts you accept, revise, or throw away.

Series

Nine stages

  1. Premise
  2. Themes & throughlines
  3. World & setting
  4. Political landscape
  5. Factions & powers
  6. Series arc
  7. Endgame
  8. Recurring cast plan
  9. Book breakdown
Book

Eight stages

  1. Book premise
  2. Arc slice
  3. Threads in this book
  4. Character arc turns
  5. Act structure
  6. Chapter outline
  7. Cast delta
  8. Continuity check
§ 03  What else is in the lens

The rest of the toolkit.

01

Character arcs as first-class objects

Want, need, lie and ghost, tracked separately from the static character profile, with turning points placed as beats on the grid. A character sheet tells you who someone is. An arc tells you where they're going and when they get there.

02

Narrator voice, per character

A voice profile — diction, cadence, worldview, verbal tics — derived from a character's own file and the scenes they appear in. Chapters name their narrator, and that voice layers into narration for those chapters.

03

Narrator style, project-wide

A tone and prose-style block that stays in context on every turn — generated either from parameters you set, or by analysing your own writing so the system's suggestions sound like the book they're going into.

04

Chronicles

Ask how two characters' relationship develops across everything you've written, or how a motif threads through the work, and get back a document that stitches the actual sources together — which then becomes an ordinary document in the project.

05

Scaffolding and derivation

Generate the book/act/chapter skeleton. Derive thread spines from what you've written. Derive character arcs. Derive beats. Every one of them lands as reviewable documents rather than as hidden state.

Series validation

The advisory audit

Two passes, deliberately separated by cost:

  • Cheap and deterministic, straight off the beat graph — dropped threads, unpaid setups, missing arc turns, orphaned beats.
  • A model pass for the judgement calls — timeline coherence, point of view, plausibility, pacing.

Findings arrive with proposed fixes you review. Nothing is ever auto-applied to your manuscript.

Provenance and canon

Every document is marked as authored — yours, canon — or generated — the system's, provisional. On top of that sits a canon status: canonical, draft, variant, or ask for a flagged continuity question. The assistant is instructed to prefer your text over its own on any conflict, and to treat a flagged document as a question rather than as a fact. Two people co-writing get a shared record of what is settled instead of an average of their contradictions.

Chat commands

Build the world without leaving the conversation

/create a world document grounded in existing material · /populate to find gaps and propose what fills them · /relationship and /thread for chronicles · /derive threads and /derive arcs for weave-board spines · /svalidate for the cross-cutting audit.

Results render in the chat and nothing is added until you accept it.

§ 04 in practice
§ 04  Mid-draft

What happens when you import a manuscript.

  1. You import, and keep working

    Analysis runs in the background and never on the save path. The editor doesn't block on a model, ever.

  2. A reverse index appears

    Every character, place, object, thread and motif, with what each is in versus merely mentioned in. Built by deterministic matching, so it's readable and correctable rather than opaque.

  3. Motifs collect what folders separated

    Thematically-linked scenes get tagged with shared theme-language, so material that belongs together but lives in five different folders can finally be pulled together.

  4. You ask a question that spans the draft

    “What has Wren actually been told about the compass, and when?” — and get an answer built from the vignettes that bear on it, with every source listed and scored.