Listening guide
How we shape stories for listening
A transparent view of the deterministic editorial work behind each Novel Aloud story page.
Published July 27, 2026 · Updated July 28, 2026 · 5 min
Start with bounded facts
Every story begins with a versioned Arcwave source bundle. It can provide identity, author, publication status, genres, content rating, chapter counts, verified audio availability, approximate listening duration, and freshness dates.
Novel Aloud does not copy chapter text, transcripts, audio objects, customer records, or storage credentials into its editorial system. When a fact is absent, the page leaves it absent instead of filling the gap with a confident guess.
Separate facts from editorial framing
Operational facts remain owned by Arcwave. Novel Aloud uses them to assemble a concise listening answer, quick facts, content guidance, commitment context, and visible FAQs.
The deterministic rules can vary sentence structure, but they cannot invent popularity, ratings, completion, author intent, listener counts, or themes that the source does not support.
Validate one complete package
Title, description, story card, answer, facts, guidance, FAQs, internal links, and structured-data inputs travel as one version. A partial result is never eligible for publication.
Validation checks schema completeness, exact numbers, source traceability, forbidden claims, maturity guidance, supported links, and the current noindex policy. A hold or blocked result keeps the last approved version active.
Publish deliberately and keep a way back
A passing version can be published only through the role-controlled editorial workflow. Publication moves one complete active pointer and appends audit evidence in the same transaction.
Rollback names an exact prior passing version. If publication or rollback fails, the current page remains unchanged instead of exposing a half-updated package.
Correct the source of truth
If a chapter count, status, audio fact, or other operational field is wrong, the correction belongs in Arcwave. A fresh source version then flows through Novel Aloud with a new bundle hash.
Editorial corrections retain the prior version, the reason, the actor, and the update time. That record is what makes the visible methodology more than a promise.