# Pre-flight Checks

> The deterministic validators that stand between a page and the air.

Glider documentation · Playout & On Air · Web page: https://cgglider.com/docs/checks/

Sections of this page: [Overview](https://cgglider.com/docs/checks.md) · [Wiring report](https://cgglider.com/docs/checks/wiring.md) · [Structure report](https://cgglider.com/docs/checks/structure.md) · [Scene & script reports](https://cgglider.com/docs/checks/scene-script.md) · [Unit report](https://cgglider.com/docs/checks/units.md) · [Working with failures](https://cgglider.com/docs/checks/workflow.md)

Four checks, three levels, one gate.

Four reports run over a page: wiring, structure, unit and scene. Each issue carries a level — failure, warning or info. A failure blocks go-live and blocks an agent from writing; warnings and info are advisory.

They run on the go-live gate, on agent writes, when a control panel is built, and on demand over HTTP so they can be wired into CI.

> **Deterministic, not clever:** These are static checks over the page document. They do not guess; every failure names a specific thing to change.