Command Daily Operations

A repeatable operator routine for using Command without turning normal daily work into production incidents.

Start-of-day operator sequence

Open Command through Access

Browser → Command

Confirm you are on https://command.iridesceux.com, not a local demo or old preview URL.

Check System Health

Command → System Health

Review Functions, D1, R2, Access identity, Broadcast Agent, HVN endpoints, and optional worker status. Distinguish required-core failures from intentionally-unconfigured optional services.

Check audit/recent changes

Command → Audit

Review recent deployment/config/content changes before touching the live schedule.

Check schedule and submissions

Command → Schedule / Submissions

Confirm the day’s programming and any creator-delivery/QC dependencies.

Check Master Control only after core health is green

Command → Master Control

Confirm selected market and monitor source before any TAKE.

Site Studio vs Code Studio

Task	Use	Who
Text, image, link, alt text, safe content override	Site Studio	Editor+
HTML/CSS/JS/function code or repo file	Code Studio	Technical Admin+
Production deployment/config	Deployment/technical workflow	Technical Admin+
Secrets	Provider-native secret storage / Command vault where appropriate	Highest-trust staff only

Create/edit content safely

Select the correct site at the top of Command.
Open the relevant module.
Make one scoped change.
Preview it.
Check links/assets/accessibility text.
Save/publish.
Open the actual staging/public URL in a second tab and verify.
Check the audit entry.

End-of-day sequence

Confirm no test graphics/alerts/ads remain on air.
Return all markets to expected normal presentation state.
Review failed/aborted broadcast commands.
Review audience/telemetry anomalies.
Record unresolved incidents/tasks.
Confirm backup/rollback information for any production deploy made that day.
Sign out if using a shared workstation; never share browser profiles.

v24 daily rundown workflow

Open Schedule / Rundown and choose the service date plus National or one local market.
Build the day privately from 12:00 AM through 11:59 PM. Program, Live Event, Standby, and Commercial Break blocks are separate types.
Attach an air-ready program master to every prerecorded Program block. Local markets may inherit National programming while carrying their own break clocks or local program overrides.
Run Day Readiness. Resolve primary-block overlaps, missing masters, invalid break clocks, and unintended gaps.
PUBLISH TO HVN WEBSITE only when the public EPG is ready. This does not put the schedule on air.
A Technical Admin uses APPROVE DAY FOR AIR after content/QC review. This still does not arm automation.
At the intended operating time, use GO LIVE / ARM THIS MARKET. Manual Live/OBS takeover remains available at any time.

Three separate gates: website publication, air approval, and automation arm are independent. Editing a draft block can never publish or air it by itself.