jD$dZddlmZddlZddZy)u The single broadcast control gate — one definition shared by every server/agent in this package. WRITE (actuating) broadcast tools — cut a scene, start/stop the stream, take the broadcast public/end it — are exposed ONLY when this returns True, and it is **default OFF**. The gate was written when a media-production partner owned the switch box and our tools sat beside a human who was doing the switching: touching his desk was simply not ours to do. **There is no longer a switcher operator.** The box is VR-owned, the broadcast runs automatically, and someone monitors it — so the case this gate was built to protect no longer exists, and the case it always allowed (a VR-owned / unmanned box, explicitly opted in) is now the normal one. It stays default-OFF anyway, and the reason has changed rather than gone: these tools can start a stream, stop it, and take a broadcast PUBLIC. That is worth an explicit act per deployment even when nobody's desk is at stake — and it must never be set in a dev checkout, where a stray agent could put a rehearsal on air. Set `BROADCAST_ALLOW_CONTROL` on the box that is actually broadcasting. Kept here (not duplicated per module) so the OBS server, the YouTube server, and the director agent can never drift on what "control is allowed" means. ) annotationsNc~tjjddjj dvS)zJTrue iff BROADCAST_ALLOW_CONTROL is set to a truthy value (1/true/yes/on).BROADCAST_ALLOW_CONTROL)1trueyeson)osenvirongetstriplowerD/srv/vr/releases/25f455cc4e75/v3/broadcast/live/broadcast_control.pycontrol_enabledrs0 ::>>3R 8 > > @ F F HLf ffr)returnbool)__doc__ __future__rr rrrrrs(# gr