Preflight Checks
Preflight is CueForge's automated safety gate. It runs before Show Mode entry to catch problems before they reach the audience. Preflight checks media file existence, trigger mapping validity, output configuration, and cue integrity. Issues are classified as blockers (must fix) or warnings (acknowledge if understood).
Preflight decision flow: blockers prevent entry, warnings can be acknowledged
What it does
Preflight runs a series of automated checks before allowing entry into Show Mode. It validates media file existence, trigger mapping integrity, output configuration, and cue consistency. Every issue is classified as either a blocker (must be fixed) or a warning (can be acknowledged if understood).
Why it matters
Live production is unforgiving. A missing audio file or broken trigger mapping discovered during the show is a crisis. Preflight exists to turn invisible problems into visible, actionable lists — before the audience arrives.
Typical workflows
- Run Preflight before entering Show Mode
- Fix all red blockers
- Read and consciously acknowledge yellow warnings
- Confirm entry only when preflight is clean
Important
Preflight catches errors that software can detect. It does not replace human judgment or physical checks.
Current limitations
- Preflight cannot detect all real-world problems (e.g., a powered-off device on the network).