One connected system, from manuscript to audio.
Marvox is not a stack of disconnected tools. Manuscript ingest feeds the CharacterOS runtime, scenes pass continuity review, and only approved work moves into voice and audio downstream.
- Ingest
The manuscript is the source
Upload parses chapter structure into a working text. Nothing downstream drafts from a blank prompt.
- Ground
Canon becomes retrievable
Canon chunks and project memory are stored as story evidence, retrieved through pgvector, never executed as instructions.
- Route
One runtime carries the work
Reader, character, continuity, quality, voice, and audio specialists share a single CharacterOS core and policy.
The runtime is the center of the system.
Canon, modes, agents, and handoff share one core. Everything the studio does routes through here, which is why a character built in chapter two still behaves the same in a scene drafted from chapter nine.
Strict source-bounded character behavior.
Limited inference from canon evidence.
Alternate outcomes with project framing visible.
Creative scene drafting with continuity intent.
Retrieved story truth
Canon chunks and project memory are treated as story evidence, not executable instructions.
Behavior boundaries
CANON, CANON+INFER, BRANCH, and WRITER_ROOM define how much freedom each workflow has.
Specialized work
Reader, character, writer, continuity, quality, voice, and audio specialists route work through one runtime.
Retrieved story truth
Canon chunks and project memory are treated as story evidence, not executable instructions.
pgvector retrieval, scoped context
Behavior boundaries
CANON, CANON+INFER, BRANCH, and WRITER_ROOM define how much freedom each workflow has.
Mode-aware prompts and guardrails
Specialized work
Reader, character, writer, continuity, quality, voice, and audio specialists route work through one runtime.
Lazy runtime, shared policy
Queryable structure
Graph, timeline, storyboard, snapshots, and world entities keep outputs tied to inspectable story state.
World and relationship surfaces
Production outputs
Scenes, voice direction, audio, and exports move forward after review.
Continuity, audio validation, export preflight
Inspect the structure, then hand off the output.
The same runtime turns the book into queryable structure and feeds production. Audio is the last step, and it inherits approved story decisions rather than fixing weak content after generation.
CharacterOS builds the operating layer
Profiles, canon memory, runtime modes, and retrieval make character behavior reusable across the studio.
Storyworld keeps relationships visible
Graph, timeline, storyboard, and world views turn the manuscript into an inspectable production map.
Scene review catches drift before audio
Cast, direction, continuity, and quality checks keep new scenes from outrunning the book.
Reviewed text
Cast, direction, continuity, quality.
Character delivery
Voice setup follows character evidence.
Output and telemetry
Generation, streaming, validation, export.
Review is built into the path, not bolted on at the end.
Continuity, storyworld context, interface parity, and audio validation each sit at the boundary they protect. A weak decision is caught where it is cheap to fix.
- 01Continuity
Review scenes before voice recording begins
Continuity validation is part of the scene workflow, so issues surface before audio production starts—not after.
- 02Storyworld
Track characters, relationships, and timelines
Story graph and world views keep entities, relationships, and narrative state visible alongside text generation.
- 03Interfaces
One runtime powers web, Word, and Google Docs
The browser app and the Word add-in connect to the same CharacterOS runtime. Both add-ins, Word and Google Docs, are in a controlled pilot.
- 04Audio quality
Audio quality starts with story quality
Voice and audio inherit approved story decisions rather than trying to fix weak content after generation.
See where the system fits your work.
Developers build against the runtime surface. Studios govern production across a team. Both run on the same connected pipeline you just read.