01
Premise
A concrete seed idea becomes source material, not prompt confetti that vanishes after one chat turn.
Control
Writer supplies, edits, or rejects the premise before machinery starts.
No paid generation is required to read this public demo.
The production system
From premise to finished manuscript, FictionOS runs the whole fiction workflow.
FictionOS is not a blank chatbot window. It is a structured production OS for long fiction: planning, voice, chapter writing, quality enforcement, memory, revision, export, and monitoring.
23
Planning steps
web/src/lib/pipeline/planningPipeline.ts:2
17
Chapter steps
web/src/lib/pipeline/stepRegistry.ts + v251 characterization tests
25
Enforcer steps
web/src/shared/services/enforcerChain.ts:1
3
Public model tiers
Claude Opus 4.7, Claude Sonnet 4.6, and Claude Haiku 4.5
60-second proof tour
Premise to export, with control and cost points visible.
02
Planning board
FictionOS turns the idea into a causal map: architecture, characters, POV, stakes, memory, and chapter plans.
Control
Writer reviews the spine before chapter prose starts.
Planning uses the connected OpenRouter key when run in-app.
03
Voice profile
Voice Studio can compare generic output against profiled author voice so style is not a mood board.
Control
Writer uploads, tests, refines, attaches, pauses, or deletes the profile.
Voice rebuild/test calls use BYOK and are visible before use.
04
Chapter draft
Chapter writing runs through the registry-driven production pipeline, not a blank chat box with amnesia.
Control
Writer chooses tier, mode, chapter count, direction notes, and when to stop.
Chapter cost varies by model, length, retries, cache, and revision work.
05
Quality finding
Programmatic checks look for repetition, explainy prose, cliches, rhythm collapse, and regression drift.
Control
Writer can accept, rewrite, inspect, or export instead of being trapped in auto-polish.
Programmatic enforcers are designed to avoid extra model calls.
06
Revision patch
Review produces auditable targets with approval, rejection, quote, and history rails before finished prose moves.
Control
Writer can run audit-only, guided revision, or controlled automation with a veto.
Revision should quote before mutating finished prose.
07
Export
Work leaves as manuscript, DOCX, TXT, EPUB, analysis, architecture, or JSON backup.
Control
Writer keeps portable copies and can delete projects.
Export is not an LLM spend event.
FictionOS should be judged by artifacts, not slogans: a plan you can inspect, a voice you can test, chapters you can read, revision targets you can approve, and exports you can keep. The author keeps taste, voice, veto power, and final judgment.
23-step planning phase
Planning
The premise becomes a continuity bible, chapter architecture, causality map, POV plan, pressure curve, and reusable handoff into chapter writing.
Voice Studio profiles can be tested, refined, and attached to projects.
Voice
The system studies rhythm, prohibitions, recurring moves, and character filters so generated prose is steered by a profile instead of a generic prompt.
25-step programmatic enforcer chain
Quality
Programmatic analyzers and enforcers look for repetition, explainy prose, cliches, filter words, rhythm collapse, and regression after polish.
Audit Only, Guided Revision, and Auto Revision modes
Revision
Whole-novel review produces accountable targets with quotes, approval states, rejection, history, and original-prose preservation.
DOCX, TXT, EPUB, manuscript, analysis, architecture, and JSON backup surfaces
Export
The product treats portability as a core workflow, not an afterthought.
Health, API, UI, alert-drill, and optional paid canary monitors.
Monitoring
Release health, public user paths, registry mode, and alert delivery have no-paid monitor coverage, with paid canaries reserved for real LLM proof.
Recovery is part of the product: generation jobs support retry, cancel, resume, approval flows, version/history preservation, and production monitors. The public story now mirrors the engineering work instead of hiding it.