The Pudding

Somewhere in your closet there’s a binder. Maybe it’s a folder on your laptop. Maybe it’s a Discord channel with three years of session recaps that only your players ever read. It contains the best story you’ve ever told — and you told it collaboratively, across dozens of sessions, with five other people who each brought a character you could never have invented alone.

It’s a novel. You just don’t know it yet.

Most collaborative fiction dies in the gaps between sessions. The game master remembers the big moments. The players remember their moments. Nobody remembers the connective tissue — the way the halfling’s offhand comment in session six became the key to the whole mystery in session twenty-two. The story exists in the collective memory of the table, and collective memory is unreliable, scattered, and mortal.

The platform fixes this by making session capture a natural byproduct of play.

Here’s how it works. You schedule a campaign session through the Calendar. Your players confirm attendance. The session happens — in person, over video, wherever. Afterward, you open the Chronicle Keeper and log the session. Not a transcript. Not a recording. A structured summary: what happened, who did what, what changed in the world.

The platform gives you a template. It asks for the scene beats — three to five key moments. It asks for character actions — which player characters drove the narrative forward and how. It asks for world changes — what’s different in your fictional world now that this session has happened. And it asks for unresolved threads — what questions are open, what conflicts are brewing, what promises were made that haven’t been kept yet.

You fill this in. It takes ten minutes. Maybe fifteen if the session was particularly dense.

Now multiply that by forty sessions. Fifty. Eighty. Each one captured in the same structured format. Character actions accumulate into character arcs. Unresolved threads accumulate into plot tension. Scene beats accumulate into a narrative with pacing, rising action, climax, and resolution.

The platform’s compilation tools can see this structure. They can identify which sessions form a coherent arc — the seven sessions where the party tracked the assassin, the twelve sessions of the war campaign, the three quiet sessions where the characters dealt with the aftermath. An arc is a story unit. A story unit is a chapter. And chapters, assembled in sequence, are a book.

You didn’t write a novel. You played one. The Chronicle Keeper helped you realize it.

But realization isn’t publication. The raw session summaries are not prose. They’re notes — good notes, structured notes, but notes. The pipeline from session summary to publishable narrative requires editorial work, and the platform doesn’t pretend otherwise.

What it does is reduce the editorial distance.

A session summary that says “Kira convinced the mountain clan leader to sign the treaty by revealing her own clan heritage” is not a novel paragraph. But it is a scene directive. A writer — the game master, or a player who happens to write, or a Guild member who specializes in narrative — can take that directive and produce the scene. The world-building is done. The character motivations are established. The plot is resolved. The only thing left is the prose.

This is where the Guild structure matters. A Chronicle Keeper Guild can include game masters who produce the raw session archive, writers who convert session directives into narrative prose, artists who illustrate key scenes through the Design Pipeline, and editors who assemble the final work. Each contributor’s role is tracked in the IP Ledger. Each contributor receives attributed credit when the work is published.

The published work goes to the Storefront. Priced at Cost+20%. The cooperative takes its twenty percent. The contributors split the remainder according to their attributed shares. The game master who ran eighty sessions doesn’t get the same share as the writer who spent two months converting them to prose — but both get credited, both get compensated, and neither gets zero.

The format is flexible. Not every campaign becomes a novel. Some become serialized fiction — weekly chapters released through the platform’s content distribution system, building an audience over time. Some become illustrated lore guides — the world-building documents that the game master created as campaign background, polished and published as reference material for other game masters. Some become audio dramas — the session recordings, if the group consents, edited into a podcast-style narrative.

Every format follows the same pipeline: capture, structure, compile, edit, publish, distribute. Every format uses the same IP Ledger. Every format generates platform credits that circulate within the cooperative.

The proof is in the pudding.

A group of seven members runs a fantasy campaign for two years. One hundred and four sessions. The game master logs every session in the Chronicle Keeper — ten minutes each, structured template, consistent format. When the final arc concludes, the platform’s compilation tools identify four major story arcs across the campaign.

The game master and two players form a writing Guild. Over four months, they convert the first arc — twenty-six sessions — into a novella. A third player, who is a digital artist, produces twelve illustrations. The IP Ledger shows four contributors with defined attribution: game master at forty percent (world-building plus session capture), two writers at twenty percent each (prose conversion), artist at twenty percent (illustrations).

The novella publishes on the Storefront. It is discovered through a Skipping Stone — a single chapter summary that hooks a reader who has never played a tabletop game in her life. She reads the Pudding version. Then the full novella. Then she joins the platform to find out if there’s a sequel.

There is. It’s being played right now, every Thursday night. And this time, the group knows from session one that the story they’re telling is a story worth publishing.

The binder in the closet was always a book. It just needed a system that could see it.

This is NOT Pudding

The Chronicle Keeper’s campaign-to-publication pipeline integrates Calendar (session scheduling), structured session capture templates (scene beats, character actions, world changes, unresolved threads), compilation tools (arc identification and chapter assembly), the IP Ledger (multi-contributor attribution), the Design Pipeline (illustration), and the Storefront (publication at Cost+20%). Guild structures support role specialization from game master to writer to artist to editor. All published works follow standard cooperative economics with transparent attribution and contribution splits.

INSERT INTO pudding_articles (
  number, title, subtitle, body_preview, session_id,
  word_count, status, created_at
) VALUES (
  173,
  'From Campaign to Novel',
  'Collaborative Game Sessions Auto-Converted to Published Narratives',
  'Somewhere in your closet there''s a binder.',
  'B083',
  1380,
  'draft',
  NOW()
);