Mission Control

Canonical implementation: MissionControl-Recoded — EventOS rebuilt as a deployable venue stack. · DeepWiki

Operator-facing role: Live event control — roster, paging FDNs, AlleycatTV playback, bounty posters, broadcast groups, ops/debug. Complements on-device firmware (PDN/FDN); does not replace game logic on players’ PDNs.

Notion vs DeepWiki vs GitHub: This page is the Alleycat-facing summary (what the stack is for, how pieces connect). For implementation depth (apps, HA integrations, MQTT fabric, deploy, CI), use DeepWiki first. When the system changes, update repo Docs/ + README.md first; DeepWiki tracks the codebase.

Related index: Open Source Software

DeepWiki (stack implementation)

<aside> 📚

Context lives here in Notion. For codebase-level docs (repository layout, Home Assistant layer, MCS / Registration / AlleycatTV / GBN / DNN, Proxmox provisioning, MQTT topic schema, testing & CI), use DeepWiki:

alleycatassetacquisitions/MissionControl-Recoded on DeepWiki

</aside>

Architecture (one screen)

Operators → Home Assistant (sidebar panels, services, automations, entities)
              ├─ MQTT (Mosquitto add-on) → FDNs, AlleycatTV Pis  [fabric: mc/dnn, mc/tv]
              └─ HTTP → Master Control Server, AlleycatTV content, GBN posters  [Proxmox LXCs]

PDN ↔ FDN (ESP-NOW)     FDN ↔ Central Server (HTTP)     HA never talks to Central directly
                          MCS = only Central HTTP adapter on Mission Control side

Home Assistant OS = control plane (VM on Proxmox). Not a second custom backend.
Companion services run on Proxmox LXCs; HA connects out — it does not host those HTTP/file servers.
MQTT broker: official Mosquitto HA add-on only (not a separate Proxmox Mosquitto LXC by default).
Panels call Home Assistant (services / websocket). They do not fetch LAN companion URLs directly.
Core Configurator holds service URLs + shared API tokens; other apps use get_url / get_extra.

Apps (products)

App	Code domain	What it does
Core Configurator	`core_configurator`	URL + token catalog for all companions
Registration	`registration`	HA face of player roster (add/edit/delete via MCS)
Master Control Server	`master_control_server`	Proxmox FastAPI; only Central HTTP adapter; Player/Role/NeoCorp JSON
Digital Node Nexus (DNN)	`digital_node_nexus`	FDN paging, LED, haptic over MQTT (`mc/dnn`)
AlleycatTV	`alleycattv`	Display playback: HA MQTT (`mc/tv`), content server on Proxmox, Pi client
Galactic Bounty Network (GBN)	`gbn`	Bounty posters + capture; poster server on Proxmox
Broadcast Group Controller	`broadcast_group_controller`	HA Areas = physical place; Broadcast Groups = command/membership sets
Bug Buster	`bug_buster`	Ops: Proxmox console, MQTT spy, health
Meru	`meru`	LLM / interactive story surface (planned)

Players are not HA devices. Players are Central records exposed via Registration + MCS. FDNs and AlleycatTV Pis are devices.

NeoCorp (Freelancer, Helix, Endline, Reboot) and Role (hunter/bounty) are owned by MCS/Central.

MQTT fabric (FDN + AlleycatTV)

Principles from repo Docs/MQTT Communication Principles.md (full detail on DeepWiki):

Only HA publishes MQTT commands (AlleycatTV content server must not duplicate the command path).