A shared dictionary of regions, each filled by an RC3 organism. Templates compose freely from these regions — they are not pinned to a canonical arrangement.
Where things are
The map, 3D viewport, or sensor frame the operator is acting on. Carries platforms, geofences, waypoints, and overlays.
Map at command-post density; a single platform-mounted camera view at platform scope; a wider area-of-operation view at swarm scope.
What is in scope
Lists the platforms the operator is addressing. Selection, status, latency, and quick health are surfaced inline.
A single detailed row at platform scope; group rollups at group scope; aggregated population counts at swarm scope.
What the platforms know
Live data from the platforms in scope — speed, position, battery, mission-relevant sensors. Fresh values are clear; stale values are flagged.
Full instrument readout at platform scope; aggregated min/max/mean at group and swarm scope; objective-level metrics at mission scope.
Who is driving
The level of autonomy in effect and the surface for changing it. Includes the active mode, the available transitions, and the consent gestures that gate them.
Per-platform mode at platform scope; group-level intent at group and swarm scope; objective gates at mission scope.
What the link is doing
Link state, signal strength, and platform health for every connected platform. Persistent — the operator never has to dig to confirm comms.
Per-link bars at platform scope; aggregated link health at group and swarm scope; mission-wide connectivity summary at mission scope.
How to stop
The primary safety affordance for the active scope. Always reachable in one tap; visually distinct from identity colour.
E-stop and override at platform scope; recall and halt at group and swarm scope; abort and pause at mission scope.
What happens when
Sequenced phases, waypoints, or objectives across time. Past, current, and upcoming states are visible together.
Sortie or patrol timeline at platform and group scope; phase ladder at mission scope; absent at swarm scope where intent replaces sequence.
What the operator opened
Inspector for whatever object is selected — a platform, a waypoint, a contact, an incident. Holds the deep view that the canvas summarises.
Platform readout at platform scope; group dossier at group scope; swarm rule editor at swarm scope; objective brief at mission scope.
Templates pick the regions a surface needs and arrange them for the operator’s task. A teleop console foregrounds the spatial canvas, autonomy state, and safety actions; a mission planner foregrounds the mission timeline and detail panel; a swarm console foregrounds the platform roster and comms strip. Same vocabulary, different emphases.
The regions do not imply position. A template chooses where each region sits, how large it is, and which variant it carries. The vocabulary anchors the operator’s mental model so new templates feel familiar from the first surface.