Viral Story Engine: A Daily Pipeline That Writes, Publishes, and Schedules Serialized Fiction
Viral Story Engine is a daily pipeline that generates serialized first-person fiction, publishes it to a site at moltogrosso.com, and schedules it to Facebook with a multi-comment cascade designed to look like organic conversation. It's one of the more unusual bets in this portfolio — content generation built explicitly as a distribution system, not just a writing tool.
Fiction works differently from utility or educational content. The hook isn't information, it's narrative tension and continuity. Could a pipeline generate genuinely serialized stories — not one-off pieces that happen to share a byline — with enough internal consistency to build a returning audience? And would Facebook's comment-driven distribution, the same mechanic behind the Facebook content engine elsewhere in this portfolio, carry fiction as well as it carries bait-style posts?
A five-stage generation engine handles it: Brief, Write, QA, Rewrite, Image, running against an LLM and feeding a "Master Story Bible" — 12 separate continuity engines and 16 character buckets keeping tone, arc, and character behavior consistent across stories instead of each one starting from a blank slate. Output flows into an Astro 5 site deployed to Vercel, and separately into a scheduler pushing posts through the Publer API to Facebook Pages as a post plus a six-comment cascade — the same "earn the reaction, not just the click" logic as the Facebook engine, applied to fiction instead of bait. A standalone Runway feed generator turns story output into video-ready prompts, feeding yet another tool in this stack.
Continuity Is the Hard Part
Anyone can generate one good story. Keeping a cast and arc consistent across dozens of daily-generated ones, with no human editor watching every entry, is the real constraint. That's the actual problem the Bible-engine system solves, and the QA/Rewrite stages exist specifically to catch a story drifting off established continuity before it publishes, not after.
Underneath the fiction framing, this is a distribution bet. The goal was never "write good fiction" on its own — it's a repeatable engine turning a story into a scheduled, multi-touchpoint Facebook presence without anyone scheduling by hand. The six-comment cascade gives it away: built to simulate the organic thread engagement that gets a post pushed further, the same mechanic the Facebook engine uses on non-fiction content.
Unclear, Honestly
92 commits over about a month, a working end-to-end pipeline from generation to publish to Facebook scheduling. Current live status is genuinely unclear — moltogrosso.com resolves but returns a 403 to automated checks as of this writing, which is different from the confirmed-dead state of HittinCorners but isn't confirmation it's actively running either. Worth a real check-in rather than a guess either way.
Frequently Asked Questions
- What is Viral Story Engine?
- An automated pipeline that generates serialized first-person fiction optimized for Facebook virality, publishes it to a paginated site at moltogrosso.com, and schedules Facebook posts with a multi-comment cascade — all from a single daily cron run.
- What is the "Master Story Bible" and why does it matter?
- A shared continuity system — 12 "Bible engines" plus 16 character buckets — that keeps generated stories consistent across a serialized run instead of each story being generated in isolation with no memory of what came before, which is what makes "serialized" fiction actually serialized rather than a pile of unrelated one-offs.
- Is moltogrosso.com still live?
- As of this writing the domain resolves but returns a 403 to automated requests, which could mean bot protection or could mean the pipeline isn't actively running — the status is genuinely uncertain rather than confirmed either way.