Creator publication, versions, and backups

Publish one linked episode

For fiction Stories, Story → Publish opens an episode chooser. Select the episode, or open

Publish from its Timeline. Publication creates an immutable revision of that episode's draft,

including its referenced cast, locations, voices, and reviewed artwork. Sibling episodes retain

their existing revisions without being recompiled or having their speech regenerated.

Unpublished siblings stay private even when their drafts are incomplete. Publish entire Story

explicitly releases every episode draft together.

Comedy checks use the current authored season ledger and character engines. Correct

the named setup, payoff, or cast inconsistency before publishing the selected episode;

the other episode drafts stay private.

Published episodes remain linked by season and episode position. Adding an episode extends the

available sequence. The episode's Versions page shows its own revisions and current revision;

publishing a sibling does not add a revision to that history. Story history records the linked

reading order and exact episode revisions. Existing sessions stay pinned to their original release.

Wait for the latest pending release to finish before publishing another episode; superseded

historical builds do not block publication. Episode publication starts from the current default

release; a non-default release does not silently become its base.

Publish lint results

Publish lint separates blocking errors from warnings and names the affected story area when it can.

Every blocking finding must be corrected before publication. Review warnings in context and record

the workflow's explicit acceptance only when the authored result is intentional. The assistant

cannot waive a finding, mark a warning reviewed, or invent a missing value. After editing the draft,

run lint again so the confirmation uses the current result.

What changed since the last publish

For an episode publication, lint and change review compare the selected draft against that episode’s current

published revision. Sound-cue changes also appear in that review before publication

freezes them. Whole-Story publication compares the whole draft. Inspect

added, removed, and modified characters, locations, events, and branches, along with the displayed

risk reasons. A high change count is not automatically an error, and “no meaningful changes” does

not replace lint; the two checks answer different questions. On a first publication there is no

earlier version to compare.

Publication changelog

Write a short changelog title that tells readers or collaborators what materially changed, then

use notes for useful detail. The title is required by the publishing workflow; it is not a place to

hide unresolved warnings or claim a fix that is not in the draft. The changelog is recorded with

the publication trail, so review it together with the exact draft being confirmed.

Confirm publication

Before confirming, check the lint status, accepted warnings, change summary, and changelog shown in

the final step. Publication creates a new immutable reader-visible snapshot; it does not edit an

older version in place. Do not confirm if a background build or validation result is still pending,

and do not retry a failed attempt until its recorded outcome is visible. Later authoring remains a

draft until another successful publication.

Publishing and story versions

Publication creates an immutable reader-visible version from the validated draft. Later edits stay

in the draft until another version is published. Existing reader sessions remain tied to their

authorized version unless the product explicitly offers an upgrade path.

Unpublishing and unavailable content

Availability can change through creator action, moderation, or platform policy. Removing public

availability does not rewrite completed transcripts or grant access to a replacement draft. For a

moderation decision or disputed restriction, use human support rather than trying to republish

through a stale link.

Backups and restore

Creator backups export the supported owned authoring data. Restore validates the package and

ownership before changing a draft; it is not a way to overwrite published snapshots, import

another creator's work, or bypass current schema and safety requirements. Keep an original backup

until the restored draft has been reviewed.