IRIDESC E UX · COMMAND
v30 · Program Primary Revision
INTERNALSTEP-BY-STEP

Go-Live Checklist

The final launch sequence. Do not use this as a substitute for the first-time setup or readiness tests.

72–48 hours before launch

☐ Command custom hostname requires Access
☐ /api/command/me returns correct identity/role
☐ Setup Doctor core healthy
☐ Fresh D1 export stored privately
☐ R2 test upload/read/delete succeeds
☐ Iridesceux staging link/legal/form pass
☐ HVN staging player/market/API pass
☐ Broadcast Agent stable on test feed
☐ Primary and backup feed verified
☐ HVN National Screen Bug/station IDs/local bugs tested
☐ Commercial Break Builder test completed end-to-end
☐ Safety Desk test performed without airing real alert
☐ Analytics telemetry verified with real external test viewer
☐ Rollback commit/deployment identified

24 hours before launch

☐ Freeze nonessential code/design changes
☐ Confirm current production branch/commit
☐ Confirm DNS/custom-domain plan
☐ Confirm on-air schedule and creator assets
☐ Confirm ad creative approvals/flight windows
☐ Confirm market Station ID assets
☐ Confirm standby/offline loop
☐ Confirm emergency contact/operator coverage
☐ Confirm no placeholder/demo/test data visible
☐ Confirm privacy policy matches actual analytics/account collection

Launch-day cutover

  1. Take one final D1 backup.
  2. Confirm Command still requires Access from a fresh Incognito browser.
  3. Attach/switch production public-site/HVN custom domains only when scheduled.
  4. Wait for Pages custom domain status Active.
  5. Test public HTTPS from a second network/device.
  6. Submit one safe public test form.
  7. Verify HVN player and all legal redirects.
  8. Verify Command is still private.
  9. Start/verify broadcast using normal rehearsed procedure.
  10. Watch external HVN player, System Health, telemetry, and support channels.

Immediate rollback/stop triggers

Stop or roll back the launch if:
  • Command is publicly accessible without Access.
  • Viewer authentication is broadly broken.
  • Forms silently lose submissions.
  • Stream playback is materially broken.
  • Emergency controls are unreliable.
  • Legal/privacy links are missing.
  • Wrong market graphics/ads/alerts are being served broadly.
  • A credential is exposed.

First 24 hours after launch

☐ Review Access/auth failures
☐ Review D1 errors and upload failures
☐ Review player errors/buffering
☐ Review audience telemetry sanity
☐ Review proof-of-play records
☐ Review support submissions
☐ Review audit log for unexpected edits
☐ Save a stable post-launch backup and tag/commit

v24 rundown launch additions

☐ Back up D1 before migration
☐ Apply MIGRATIONS/v23-program-playout.sql if not already applied
☐ Apply MIGRATIONS/v24-rundown-traffic.sql exactly once
☐ Build a complete staging National day from 12:00 AM–11:59 PM
☐ Publish staging EPG and confirm public HVN schedule changes only after publish
☐ Approve day for air and verify it still does not air while automation is disarmed
☐ Arm staging and verify scheduled file starts
☐ Schedule a National commercial pod over a prerecorded file and confirm the show resumes without skipped content
☐ Schedule a local-market substitution and verify only that market receives the local pod
☐ Verify local EPG inheritance and a local program override
☐ TAKE LIVE / OBS, verify live feed, then RETURN TO SCHEDULE
☐ Verify HVN National Screen Bug transparency/hold over moving program video
☐ Verify both Local Program Confidence and Public Confidence