Answers stay tied to the book
Reader-facing Story Q&A is most compelling when it shows evidence and boundaries instead of open-ended generation.
For Readers
Ask the book a question. Get an answer it can prove.
Readers can open character chat, grounded story Q&A, and demo-first exploration before they ever need to create a project.
Grounded answercanon-safe
Marvox Canon Reader
Does Alice drink the potion before or after eating the cake?
Alice drinks the contents of the bottle labeled "DRINK ME" first. After shrinking, she realizes she cannot reach the key on the table, and only then discovers a glass box under the table containing the cake labeled "EAT ME".
Citations
"...she found a little bottle on it... tied round the neck of the bottle was a paper label, with the words 'DRINK ME'"
"Soon her eye fell on a little glass box that was lying under the table: she opened it, and found in it a very small cake, on which the words 'EAT ME' were beautifully marked..."
Explore first. Create only when ready.
Readers need the shortest path to trust: see the demo, ask grounded questions, understand the characters, then decide whether to enter a workspace.
- 01
Open a read-only project
Start with the public demo so the product can be understood before upload, payment, or setup.
- 02
Question the story
Use grounded Story Q&A to see answers that are framed around the manuscript instead of generic chat.
- 03
Inspect characters and context
CharacterOS and reader surfaces show how character behavior and story evidence stay connected.
- 04
Move into a workspace
When exploration turns into creation, signup keeps the reader path instead of dropping visitors into a generic screen.
Why it answers back
A grounded answer shows its evidence, then stops where the book stops.
Readers get a safe path into any storyworld — start with the demo, ask grounded questions, explore characters, and only enter a workspace when you're ready to create.
What you asked
Does Alice drink the potion before or after she eats the cake?
A plain question, the way a reader would actually ask it.
What the book answers
Story Q&A frames the answer around the manuscript and shows the lines it leaned on, so you can check the work instead of taking the system at its word.
Grounded Q&ACitations in viewCanon-safe boundaries
Trust comes from seeing the story answer back.
Readers get exploration and evidence first, without authoring controls or studio operations crowding the path.
Try the storyworld before setup
The public demo gives readers a way to inspect Marvox before they upload a manuscript or create a paid project.
Characters are more than a chat box
CharacterOS keeps profiles, memory, and story context together so readers can see why an answer makes sense.
Creation is a next step, not a wall
The path to signup stays clear without making payment the proof point.
Common questions from readers.
Can I try Marvox without paying?+
Yes. The public demo is the fastest way to understand Marvox before creating a project.
Are answers actually from the book?+
The reader experience focuses on grounded Story Q&A and Canon Reader surfaces that keep answers tied to manuscript context.
What happens after the demo?+
Readers can create a workspace when they want to upload or build from their own material. The signup path preserves the reader context.
Is this the same as character chat?+
Reader exploration can include character understanding, but grounded story answers come before deeper authoring or production tools.
Start with a question, not a sign-up.
Open the demo, ask the story something, and read the answer it can back up. Create a workspace only when you want to bring your own book.