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.
Static proof path
One story moving through the FictionOS operating system.
This is demo-safe static content. It shows what the product coordinates without claiming a live customer case study or fabricated benchmark.
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.
01
Premise
A forensic accountant notices the same wire transfer leaving her dead father's account three years after his funeral. The amount is the exact cost of his casket.
02
Architecture
The planning pass turns that premise into characters, stakes, causality, false victory, pressure escalation, chapter outline, and continuity constraints.
03
Voice
Voice Studio constrains the prose toward the author profile: sentence rhythm, forbidden moves, image families, register, and the kind of humor or restraint the author actually uses.
04
Chapter excerpt
The first transfer had gone out at 03:17, which was rude of it. Her father had always believed bad news should keep office hours.
05
Quality pass
The analyzer/enforcer layer checks for repetition, explainy prose, body-language cliches, filter words, flat scene motion, and polish regressions.
06
Revision target
The review center can flag a chapter-level target, quote the likely cost, ask for approval, preserve the original, and write history when the patch lands.
07
Export
The manuscript can leave as DOCX, TXT, EPUB, manuscript format, architecture, analysis, or JSON backup so the writer is never locked in.
Generic AI prompt
"Write chapter one of a thriller." The model guesses the structure, the voice, the continuity, the cost, the revision standard, and the next chapter handoff.
FictionOS workflow
Premise is planned, voice is attached, chapter context is assembled, prose is generated, quality gates run, memory updates, revision targets remain accountable, and exports preserve the work.
What to inspect
Can you see a real premise, architecture, voice constraint, prose excerpt, revision target, and export path?
What is static
This page uses demo-safe artifacts and does not claim customer outcomes, testimonials, or benchmark superiority.
What is product proof
The workflow sequence mirrors the actual app surfaces writers use after signup.