Architecture and ownership
The game consumes events and reports results; it does not own hardware or commercial policy.
Chain
Controller → RS-485 daemon → Launcher → Game SDK → game. Console operates sessions and Launcher owns their lifecycle. Agent installs permitted artifacts. Cloud owns the internal catalog, validation, signing, publishing and entitlements.
Game boundary
A game must not open RS-485, read Agent secrets, write calibration or decide launch eligibility using its own flag. Lighting is requested through SDK capabilities. Internet connectivity must not be required to render an already started offline session.
HTML5 and Unity
The Linux Unity process reads a launch file; a browser needs a trusted manifest-delivery mechanism. The JavaScript library is not itself a browser Runtime Host. Installation, kiosk mode, display assignment and secure manifest delivery require separate integration acceptance. This portal release does not modify Launcher or controller firmware.