IRIDESC E UX · COMMAND · v32

Program Cue Sheets & Timed Traffic

Attach commercial breaks and screen bugs to exact content timecodes inside uploaded HVN programming.

Content-time rule

Cue timecodes follow the program playhead, not the wall clock. If a two-minute break pauses a show, later cues move two minutes later on the broadcast clock while remaining locked to their original content moment.

00:01:32  SCREEN BUG — Opening sponsor
00:06:48  BREAK A — 2:00
00:18:05  BREAK B — 1:30

Build a timed break

  1. Ad Inventory → upload and approve each commercial creative.
  2. Break + Cue Builder → build the reusable break clock in the exact ad order.
  3. Program Cue Sheet → choose the uploaded program and market.
  4. Enter the program timecode.
  5. Choose Commercial Break and select the saved break clock.
  6. Save Program Cue.

Build a timed screen bug

  1. Ad Inventory → approve an HVN or paid screen-bug creative.
  2. Program Cue Sheet → select the program, market and timecode.
  3. Choose Screen Bug, select the creative and optionally override its duration.
  4. Save Program Cue.

Screen bugs do not pause the program timeline.

National and local substitution

National cues inherit into local markets. A local cue at the exact same cue type and content timecode replaces the National cue in that market. This allows a New York ad pod to substitute a National pod without rebuilding the whole program cue sheet.

Clock-runtime protection

The Day Readiness audit calculates the commercial hold added by the effective cue sheet. If the rundown slot is shorter than the remaining program runtime plus those commercial holds, Approve Day for Air is blocked. Extend the program block end time before approving.

Manual priority

Manual Master Control remains authoritative. An already-live manual commercial break or manual screen creative is not replaced by an automatic program cue.

Database upgrade

npx wrangler d1 execute iridesceux-command --remote --file=MIGRATIONS/v32-program-cue-sheets.sql

Back up D1 first. On an existing deployment, apply the migration before deploying v32 HVN/Command code.

Rehearsal

  1. Use a short uploaded test program.
  2. Slot Break A after an opening/theme section.
  3. Slot a screen bug later in the content.
  4. Slot Break B after that.
  5. Confirm Break A pauses/resumes the exact program position.
  6. Confirm the later bug and Break B remain locked to their content timecodes.
  7. Create one local override and confirm only that market receives it.
  8. Check Day Readiness has zero invalid cues and zero cue clock shortfalls.

← Documentation index