RC3 Template

Operator console

The anchor template for single-platform robotics operations. Composes the three RC3 signature organisms — autonomy mode selector, comms / health strip, safety actions — over a stylised tactical canvas. One operator, one platform, the full RC3 vocabulary in one screen.

stable

Design principles applied

Safety reachable in one tapRC3 behavioural invariant 1

Safety actions anchor at the bottom-right of the canvas regardless of autonomy state, waypoint progress, or active panel. E-stop never moves between modes — operators acquire it without re-orienting.

Comms / health always visibleRC3 behavioural invariant 2

The comms / health strip sits in the top-right and persists across every console state. Link, signal, battery, and GPS lock are simultaneously visible — degradation surfaces before it becomes an outage.

No mode-switch via accidentRC3 behavioural invariant 4

Climbing the autonomy ladder requires a deliberate second tap within three seconds; the destructive safety action requires the same gesture. Descending toward operator authority — and the recoverable secondary actions — are immediate.

Predictable information placementC3 principle

Identity rule at the top, autonomy top-left, comms top-right, safety bottom-right, telemetry bottom-left. The arrangement is invariant across single-platform consoles so an operator's overlearned spatial map remains correct under load.

Preview

View at viewport scale

RC3/ OPERATOR CONSOLE

SINGLE PLATFORM · UGV-04

500 m

Autonomy

platform·UGV-04

L1SUPERVISEDOP-IN-LOOP

UGV-04LINKBATT 78%GPS LOCK

UGV-04SPD3.2 m/sHDG048°BATT78%ROLL-1°PITCH+4°SLOPE+8°

The autonomy rail discloses on the chevron; climbing arms a transition, descending commits immediately. The safety primary requires a second deliberate tap to fire. The console keeps its fixed operator layout on narrow screens — scroll horizontally to pan across it.

Code

The console is one file. Copy it into your project, swap the stylised canvas for your real map engine, and wire the organism callbacks to your platform backend.

tsx

import { OperatorConsole } from "@/templates/rc3/operator-console";

export default function YourConsole() {
  return <OperatorConsole />;
}

Notes

What's customisable

The platform — single-platform context here; switch organism scope props to "group" / "swarm" / "mission" for broader command contexts (gates which actions and aggregations surface)
The autonomy ladder — pass your own rungs array to AutonomyModeSelector. The default loop-position taxonomy (L0 MANUAL → L3 AUTONOMOUS) is a placeholder
The tactical canvas — currently a stylised SVG (grid + geofence + route + waypoints). Substitute your real map (Leaflet, Mapbox, MIL-STD-2525 renderer) here
The telemetry HUD — pass your platform's live state. Set domain to the platform class so labels resolve correctly (ALT vs ELEV vs DEPTH)
Organism callbacks — onTransition on the autonomy selector, onAction on safety actions; wire to your backend

What's intentionally fixed

The identity rule at the top — every RC3 surface carries it (1.5px Ember top border + signature dot + RC3 mark + active module name)
Organism positions — autonomy top-left, comms top-right, safety bottom-right, telemetry bottom-left. Invariant across single-platform consoles
C3 dark mode — operator-canonical regardless of docs-site mode
data-pack="rc3" on the outer wrapper — activates Ember as the accent semantic token for anything inside that reads from --prizm-color-accent

RC3 organisms used

Autonomy mode selector, Comms / health strip, Safety actions, Telemetry HUD. Four organisms cover the four corners. The fleet overview template composes a broader set — platform roster, platform detail, video tile — for multi-platform command. A mission planner template is planned.