Concepts
How RC3 thinks about commanding, behaving, and composing. Three shaping rules that hold across every surface — independent of layout.
Command contexts
What are you commanding right now?
A spectrum from single-platform direct teleop to mission-level intent. Components are context-aware — the autonomy ladder, telemetry surface, and safety actions adapt to whether you are addressing a platform, a group, a swarm, or a mission.
Behavioural invariants
What must always be true on an RC3 surface?
Five rules. Safety reachable in one tap, comms always visible, active context unambiguous, no accidental mode-switch, telemetry never silently stale. Properties of every RC3 surface, not opt-in patterns.
Surface regions
What is each region of the surface called, and what fills it?
A shared dictionary of regions — spatial canvas, platform roster, telemetry, autonomy state, comms / health strip, safety actions, mission timeline, detail panel — each linked to the organism that fills it. Templates compose from the dictionary, not from a canonical layout.