Live · phase 7
Phase 7 of 10

Live

Run show, monitor quality, capture incidents.

Family LiveToken #FF0000Duration Short
A

The intent

Why this phase exists

The moment. We run the programme, hold the quality, handle anything that comes up, and capture everything. This is what the whole lifecycle has been building to.

Exit gate

The programme runs to completion, primary and backup recordings are confirmed, and the audience has been supported throughout.

B

The work, by actor

Our people

Craft & judgement

Craft, judgement and client-facing approval.
  • Event Manager — Manage client communications, approvals and escalations without disrupting production.
  • Marketeer — Monitor attendance, engagement and sentiment; respond to audience feedback.
  • Producer — Drive programme execution: intros, handoffs, speaker timing and continuity.
  • Technical Production — Operate live video, switch sources, maintain quality, handle incidents fast.
  • Technical Support — Support viewers, resolve access issues and triage platform incidents immediately.
  • Technical Support — Moderate Q&A, chat and polls.
  • On-site AV — Run QR check-in, control cameras, confirm ISO recordings.
  • Photographer — Ingest photos directly into WDS.
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.
  • System — Restream to LinkedIn where used.
C

What the client gets

Delivered

A broadcast that runs properly. Quality held, incidents handled quietly, the audience looked after, and every frame captured with a backup.

D

The safeguard

What could go wrong

The primary capture path drops mid-session and we lose the recording.

Why it won't

ISO recordings from every camera and an enforced backup mean there's always a clean source to fall back to.

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.