← Back to studio
📚

Novel Engine

Long-form fiction that remembers. A four-stage engine — plan, outline, draft, polish — with story state tracked across every chapter of the book.

Status · Beta Korean & English Views —
Seven-stage engine

From canon to approved chapter.

Each stage has its own agent and its own gate. Nothing advances to the next stage with open defects — and no prose becomes canon without a human verdict.

01 · INTAKE

Canon ingestion

Locked chapters, character/object/clock/disclosure state — a bounded brief of what is fixed, unknown, and unreleasable. Original canon is read-only.

02 · REVERSE

Reverse design

From the chapter's end-state backwards: gain, cost, opponent's best response, broken assumption, and the earlier setup that makes the reversal fair. Approved before prose.

03 · BEATS

Beat & outline

36-beat Crucible planning + scene cards: action, planted detail, counter-move, handoff. No plot point enters outside the outline.

04 · VOICE

Voice lock

Style-profile JSON and voice samples become chapter constraints: POV, cadence, dialogue balance, withholding rules. Constraint, not imitation.

05 · DRAFT

Scene drafting

Scene-level drafts with state saved after each scene. Invented details are flagged, never silently canonized.

06 · QA

Style gates

Local checkers: ≥10,000 characters incl. spaces, dialogue ratio, narrative-sentence metrics, ten-term restricted scan. Numbers flag, humans decide.

07 · CANON

Canon promote

Human-approved release updates the continuity ledger, foreshadowing schedule, story bible, and patch log. Proposals stay proposals until signed.

Features

Continuity is the product.

🧠

Story state ledger

Character knowledge, relationships, injuries, items, timeline — tracked as structured state, injected into every drafting call.

🎭

Character voice locks

Per-character diction, verbal tics, and register are profiled at planning and enforced during editing.

🔁

Serialized release

Episodes ship on a cadence: outline ahead, draft behind, polish at the frontier. Cliffhangers are engineered, not accidental.

🌏

Bilingual

Native Korean web-novel workflow with English output pipeline — style, honorifics, and idiom checked per language.

🛡️

Human approval gate

The author approves every chapter's final text. Agents never sign off on themselves.

📖

Reader feedback loop

Comments and read-through metrics feed the next arc's planning stage as scored signals.

Live demo

The engine thinking out loud.

A looping excerpt from a sample draft pass — generated on the site by the studio's prose demo reel.

timeline · ch.12 POV · first mood · dread open threads · 3 canon events · 148 drift · 0.0%
Continuity engine

Every chapter remembers the book.

Setup, escalation, and resolution stay locked to one evolving state ledger.

Setup

She hides the letter before dawn; the house keeps her secret.

Escalation

The detective finds the letter — now three people have motive to lie.

Resolution

The letter resurfaces in court, and the house finally tells the truth.

Production record

One chapter, seven passes.

Our latest approved chapter (Chapter 3) took seven drafts to clear every gate — each rejection archived with its reason, never silently overwritten.

Pass 1 · rebuilt: scope resetPass 2 · archived: direction missPass 3 · rejected: reading qualityPass 4 · rebuilt: voice re-analysisPass 5 · over-explained → constrainedPass 6 · too heavy for the openingPass 7 · APPROVED

What the gates check

≥10,000 characters incl. spacesdialogue ratio (~39%)narrative sentence metricsrestricted-term scan · clearcontinuity ledger · patched & approved

Numbers from our local checkers on the approved draft: 10,471 characters, 39% dialogue, scan clear. A passing number never replaces the human verdict — the founder reads every version.