Module guide

Modules connect to Mainframe independently. Their entities appear in the same Fleet, 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.

Module	What you get	How to use it
world-sim	Virtual aircraft, camera feeds, radars, tracks, sites, and environment	Select virtual aircraft normally. Open simulator administration for scenarios and world controls.
auto-operator	Mission coverage suggestions or automatic dispatch	Inspect mission assignments and Alerts proposals. In staging, only SIM-STG-* world-sim aircraft are eligible.
autel	Real controller/aircraft telemetry and video	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. See Connect real aircraft.
weather	Site weather from an external feed	Select the relevant environment entity and check freshness. A stale cached value is not a new observation.
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 review items	Start an authorized session on a camera and triage its results in Review.
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.

Weather, link failures, GNSS interference, and detection scenarios change simulated observations. Missions and rules 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.