Module guide

Modules connect to Mainframe independently. Their entities appear in the same Assets, Map, Video, and analysis panels as other data. Use System for operational health and Grafana for deployment diagnostics. Module administration pages are separate surfaces linked through the module’s advertised URL; administrators open them from the command palette (Open Module Page); other users do not see them.

Module	What you get	How to use it
world-sim	Virtual aircraft, camera feeds, radars, detections, and sites	Select virtual aircraft normally. Open simulator administration for scenarios and world controls.
auto-operator	Automatic mission dispatch	Inspect mission assignments and Events. In staging, only SIM-STG-* world-sim aircraft are eligible.
autel	Real controllers hosted by this deployment: telemetry, video and control	Administrators add/edit RC logins and aircraft in Assets → Manage Autel controllers. Select a connected aircraft for video and telemetry; manual control requires a lease and an explicit engage. See Connect real aircraft.
vanagas	Read-only view of aircraft another system (vanago-akis) is flying	Watch telemetry, video, recordings and health alerts; entities carry the OBSERVE chip and accept no commands. Runs alongside autel.
vanagas-phones	Read-only phone locations and camera feeds from vanago-akis	Choose the phone in Video or Video Wall. Camera, HDMI and IP camera are separate feeds with separate recordings. Check the location age in Selection; an online phone can have an old GPS fix.
radar-net	External radar devices and detections	Inspect them on Map and associated sensor views; check feed health if updates stop.
detections	Vision-analysis sessions and captures	Start an authorized session on a camera and annotate its captures in Captures; ask it to annotate any capture.
assistant	The on-page assistant’s model	Open the Assistant panel (⌘J) and ask for something Terminal can do; approve the cards that move aircraft. See Assistant.
TAK	Imported contacts and configured CoT export	Use the administrator’s certificate and mapping setup; this bridge does not replace every feature of a full TAK server.
system	Core and module operational health	Open System to inspect the backend serving the workspace.

Simulator controls

The simulator admin page lets you inspect world state and run configured scenarios. Mutating operations require its separate admin token. A reseed regenerates the world while retaining onboarded structure. Factory reset removes the persisted simulator overlay, so use it only as part of a coordinated data reset.

Link failures, GNSS jamming, and detection scenarios change simulated observations; GNSS jamming degrades every aircraft’s satellite count. Detections and incursions spawn along the simulated world’s own AO outline (it does not read Mainframe’s AO). Missions and markings remain Mainframe documents. Rebuilding a simulator container should not clear those documents or create a new real-aircraft identity.

When a module is unavailable

Entities may remain visible with an offline status and retained history. Check the module connection and upstream health before treating the last measurement as current. Ask the deployment administrator to enable a missing module rather than changing the browser’s Mainframe URL to a module port.