Post · phase 8
Phase 8 of 10

Replay

Process recordings and publish replay assets.

Family PostToken #0284C7Duration Long tail
A

The intent

Why this phase exists

Turn the live moment into a durable, atomised content estate. Published, chaptered, distributed, while attention is still hot. A broadcast is a moment; a replay estate is an asset.

Exit gate

Every session is published with correct metadata, permissions and URLs; chapters and segments resolve; stakeholders are notified.

B

The atomisation flow

Replay is a fan-out: one recording becomes many addressable assets. Colour shows who owns each step — the platform ingests, an agent cuts, our people approve, the platform publishes.

One recording in · many assets out
Human · craft & approvalAgent · scale, owned by a humanSystem · deterministic
The agent cuts at scale, but nothing reaches the client until a named human approves. That gate is the difference between fast and reckless.
C

The agent → human handoff

Every agent task runs the same governed loop. The agent is triggered, it drafts, a named human reviews, and only then does it publish. Same shape in every phase.

The governed loop
D

The work, by actor

Our people

Craft & judgement

Craft, judgement and client-facing approval.
  • Producer — Review edits, chaptering and titles; confirm speaker approvals captured.
  • Marketeer — Set the retargeting plan and decide which segments lead distribution.
  • Technical Production — Validate recordings, audio mix, graphics, captions and encoding quality.
Our agents

Scale & speed

AI drafts; a named human owns and approves.
  • Producer — Auto-chapter sessions, cut segment URLs, generate quote cards per chapter.ownerProducer · trigger: on publish
  • Producer — Draft chapter and session descriptions for the agenda.ownerProducer · review: Producer before client-facing
  • Marketeer — Sequence stakeholder notifications and follow-up nudges.ownerMarketeer · trigger: on publish
Our platform

Reliability

Deterministic WDS behaviour, no actor required.
  • Technical Support — Publish assets in WDS; confirm metadata, permissions and playback links.
  • System — Assemble chapters, segments, slides and photos onto session pages.
  • System — Generate per-session branded download links.
E

What the client gets

Everything fans out onto one place — the session page — the artefact the client and their audience actually use.

Session page · anatomy
Published estateEvery session live, correct metadata
Chaptered sessionsNavigable chapters per session
Segment URLsEach segment on its own link
Quote cardsPer-chapter graphics, brand-applied
Branded downloadsPer-session video downloads
NotificationsSpeakers & sponsors, nudge-tracked
F

The safeguard

What could go wrong

Replay turnaround stalls because source files arrive in a heavy format.

Why it won't

Contingency uploads are enforced in H.264, not ProRes, and ISO recordings give a clean fallback to cut from.

G

The thread continues

Wavecast Phase Playbook · internal conceptual reference
Phase tokens bound to the Colour Registry · wheel engine v1.3 · multi-actor delivery model.