Resources
These short guides are written to make the product model more understandable, not to pad the site with thin placeholder content.
When multiple playlists exist for one branch, the system must still produce one effective answer. The product definition uses status, date range, priority, update order, and a final deterministic tie-breaker to keep playback predictable.
The player is designed to keep the last valid playlist, template, and assets in local cache. That matters because branch communications cannot depend on perfect connectivity or a perfect backend window.
QR and manual pairing, heartbeats, snapshot requests, queue inspection, and explicit command acknowledgements make the device fleet manageable after rollout, not only on day one.