Live · phase 6
Phase 6 of 10

Pre-Live

Execute preflight checks and confirm readiness.

Family LiveToken #CF3A14Duration Moment
A

The intent

Why this phase exists

The last two hours. Pre-flight checks on everything, final speaker checks, go/no-go. This phase is short and it's all readiness.

Exit gate

Every system has passed pre-flight, speakers are checked in and ready, the support queue is open, and go/no-go has been called.

B

The work, by actor

Our people

Craft & judgement

Craft, judgement and client-facing approval.
  • Event Manager — Confirm all stakeholders present, decisions final, and execute go/no-go.
  • Marketeer — Send final reminders, update socials, monitor attendee questions.
  • Producer — Run speaker checks, cue timings and lock programme messaging.
  • Technical Production — Run pre-flight: ingest, audio, graphics, comms, monitoring across all systems.
  • Technical Support — Verify access, player state, moderation tools and that support channels are open.
Our agents

Scale & speed

AI drafts; a named human owns and approves.
No agent tasks in this phase.
Our platform

Reliability

Deterministic WDS behaviour, no actor required.
No system tasks in this phase.
C

What the client gets

Delivered

Confidence. Everything's been checked, the speakers are ready, and someone has made an explicit call that we're good to go.

D

The safeguard

What could go wrong

We go live with an unchecked ingest or a speaker who can't connect.

Why it won't

Pre-flight is a checklist, not a vibe. Nothing goes live until every line on it passes.

E

The thread continues

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