Operator-readable documentation for the automation stack
Not customer-facing. Lives next to the live dashboard so when something breaks at 6:55 PM and there's a booking starting at 7, the operator can fix it without paging vendor support.
- Architecture overview — what's in the stack (smart-plug → monitor → PC → simulator software → ball-tracking). Diagram + 2-paragraph explanation.
- Booking lifecycle — what commands fire when (10 min before start: power on → 5 min: wake monitor → 1 min: launch sim → at end: graceful shutdown → 30 min after end if idle: power off).
- Common failures — power-on timeout (vendor API slow), monitor wake fails (HDMI handshake glitch), sim launch hangs (license server slow), ball-tracking miscalibrated (operator override). Each with a "what to check" + "what to try" checklist.
- Hardware sync explained — what the "Last sync 18s ago" tile actually polls, what stale means, what a sync failure indicates, how to manually re-sync.
- Per-vendor runbook — Trackman-specific quirks, Foresight-specific quirks. Anchored sections for each.
- Emergency contacts — vendor support phones, on-call engineer rotation, the operator's own escalation path (operator → owner → support).
- Recent failure history — last 7 failures across the club with timestamp + root cause + resolution time. Looks for patterns.
- Versioned — runbook is a living doc; shows last-updated date + edit history.
Backend wiring pending. Authored in Markdown; rendered to HTML; per-club customizable. GET /operator/automations/runbook in the live app.