Release

The candidate can remain local forever and still be finished. Release begins when the editor chooses to put those exact bytes before an external audience, with a destination and an attributable approval.

Review before effect

Source support, claims, voice/likeness authority, privacy/Portal use, accessibility, asset admission, and render checks supply their own receipts. Publication additionally binds candidate digest, destination, audience, visibility, schedule, disclosures, cost, and approving Principal.

broadcast.publish_draft@2 and broadcast.publish_public@2 are distinct effects over PublicationCandidate@2. Each pins idempotency key, payload/request digests, destination identity, reconciliation lookup, and PublicationReceipt@1. A lost acknowledgement leaves unknown remote state until inspection resolves it. Browser automation supplies no authority for an untyped retry.

broadcast.correct_publication@2 creates a forward correction. broadcast.takedown@2 requests removal while preserving the publication and receipt history. Platform refusal, expired authority, a changed candidate, uncertain remote state, or a failed gate returns its exact blocker.

Restart resolves pinned Pattern, source, handoff, script, timeline, renderer, adapter, and receipt revisions. Snapshots, rejected renders, candidates, destination receipts, and analytics retain separate policies. Deletion inventories derivatives, requests authorized remote removal, and preserves a content-free receipt; feeds and caches may retain copies.

Proving package

Before testing an external release, prove its local candidate. Build a three-to-five-minute piece from frozen sources: linked claims, article/script, local narration with back-transcript, admitted visual/music/language/picture-sound bundles, captions, explicit timeline, deterministic render, bounded repair, EditorialPackage@2, and PublicationCandidate@2. The fixture makes no platform call.

Return to Broadcast, or inspect the local candidate in Render.