ZONE 01
OFFLINESelect a camera inputDirect browser feed · OBS not required
PEOPLE—OBJECTS—MOTION—
LIVE OPERATIONS · DIRECT CAMERA MODE
Zone cameras and local AI monitoring
ACTION 1 · CAMERA ACCESSGrant camera access so SYN can enumerate the Windows video inputs.
ZONE 02
OFFLINESelect a camera inputDirect browser feed · OBS not required
PEOPLE—OBJECTS—MOTION—
ZONE 03
OFFLINESelect a camera inputDirect browser feed · OBS not required
PEOPLE—OBJECTS—MOTION—
ZONE 04
OFFLINESelect a camera inputDirect browser feed · OBS not required
PEOPLE—OBJECTS—MOTION—
PLUSH SYNDICATE · SYN OPERATIONS
Facility intelligence.
Atmosphere control.
Live production.
The browser now handles direct camera capture and local common-object monitoring for supported devices. The physical workstation remains the execution layer for OBS, network-camera ingestion, audio, lighting, displays, and protected hardware control.FACILITY CONTROL · SIMULATION
Broader control-plane prototype
SYN OPERATIONSLIVE FACILITYCONTROL-PLANE SIMULATION
- Mode
- assisted
- Event
- PLUSH LIVE · DEMO
- Recording
- ON · SIM
- System
- SAFE
CAMERA WALL4 INPUT PROTOTYPE
ANONYMOUS TRACKS · SIMULATEDDIGITAL FACILITY MODELONE ROOM · FOUR ZONES
UPDATED 1.2s AGOEXITEXIT
ENVIRONMENT CONTROLMAIN FLOOR
OBSERVABLE STATESYN FREQUENCY78/100
- Movement
- 81
- Music response
- 76
- Social interaction
- 72
- Room balance
- 82
- Preference match
- 79
CAM 2Main Floor · WideLocal OBS connection required
PROGRAM · SIMULATIONVIP + BarNo public stream is active
SYN RECOMMENDATIONS3 PENDING ACTIONS
APPROVAL QUEUEMain-floor movement rose 14% while Camera 4 retained a clear wide composition.
Dance-floor occupancy is above 30, movement energy is 81%, and BPM is within the approved scene range.
The anonymous track remained near a restricted boundary for 18 seconds. Identity is not required for review.
Main-floor movement rose 14% while Camera 4 retained a clear wide composition.
CLOSED-LOOP OPERATING SYSTEM
Observe the facility. Control only what is approved.
Cameras, microphones, check-ins, sensors, schedules
Confidence-based perception and live facility model
Rules, operator context, risk, and approval boundaries
Music, lighting, screens, OBS, and alerts
Live experience, recording, broadcast, and deliverables
Event outcomes, equipment health, and corrected rules
THE CORRECT SYSTEM BOUNDARY
One interface. Three operating responsibilities.
Direct browser-visible camera capture, local object detection, zone reports, PLUSH ID, roles, venue maps, rules, history, analytics, permissions, and deliverable records.
DIRECT CAMERAS · LIMITEDOBS Studio, RTSP and network-camera ingestion, audio processing, lighting and display control, recording, storage, and emergency controls.
HARDWARE REQUIREDA protected local service creates the outbound authenticated connection, translates approved commands, and returns telemetry and acknowledgements.
DEVELOPMENTSYN VISION · LIMITED
Observe activity without turning every guest into an identity record.
The live module reports people counts, supported common objects, and movement locally in the browser. Facial recognition and identity inference are not active. More advanced anonymous action classification remains a separate development layer.- Classify observable activity with confidence—not certainty.
- Do not infer legal identity, personality, character, intention, exact emotion, intoxication, or cup contents.
- Keep camera frames on the operating device and retain only objective report text.
- Require human review before any report is treated as an incident record.
MANDATORY SAFETY RESTRICTIONS
Automation never outranks physical safety or accountable human control.
MUSIC RIGHTS ARCHITECTURE
Discovery, venue playback, and broadcast media remain separate lanes.
Catalog search and permitted operator playback require MusicKit authorization and server-held credentials. The browser never receives the private signing key.
Music played to guests uses appropriate public-performance licensing. A personal streaming subscription is not represented as the venue license.
Recorded and streamed output uses owned, commissioned, directly licensed, or properly cleared compositions, masters, and stems.
FIRST OPERATIONAL VERSION
One room proves the complete loop.
Four cameras · PLUSH ID check-in · one room microphone · one OBS installation · one lighting universe · two displays · one audio zone
Anonymous tracking · standing · sitting · walking · dancing · probable motion classifications · occupancy · movement energy · room-frequency score
OBS scenes · simulated recording · lighting scenes · BPM rules · screen layouts · manual · assisted · controlled-autonomous modes
Master and isolated recording plan · clean audio · event timeline · occupancy report · highlight markers · social export queue
STAFF ATTRIBUTION
Every command belongs to a person or an approved automation rule.
Real operation requires passkeys or multifactor authentication, least-privilege roles, event-scoped access, signed commands, acknowledgements, immutable action records, and revocation.FORMAL PRODUCT DEFINITION