Robotics & Autonomy
An extension pack for command and control. One vocabulary across the full spectrum — from single-platform teleop to mission-level intent.
Identity
The signature colour, schematic iconography, and the identity rule that carries RC3 into any host.
Concepts
Command contexts, behavioural invariants, and the surface regions that templates compose from.
Components
Autonomy mode, comms and health, safety actions, telemetry HUD — the organisms RC3 adds to C3.
Templates
Operator console and the anchor arrangements that compose RC3 organisms into a working surface.
A live window into what the swarm sees.
Perception view is RC3’s live 3D canvas — the consolidated picture a robot swarm builds of its surroundings, with areas of interest, layer toggles, and per-source freshness so a held frame never reads as live.
RC3 frames the surface and ships a dependency-free reference renderer; a host map or vendor engine can take over the 3D through a render delegate.
One attribute, two CSS imports.
RC3 layers on top of C3 without forking. Set data-pack="rc3" on the surface that wraps the RC3 application, import the two RC3 token files alongside your C3 ones, and the accent semantic tokens flip to Ember. Surfaces, typography, radii, shadows all inherit from C3 unchanged.
RC3 is consumed the same way the rest of PRIZM is: copy the organism source files into your project, build with React. Host it however your environment requires — a Next.js app, a Vite app, embedded inside an existing system through whatever bridge your host supports.
/* in your global CSS */
@import "@prizm/tokens/c3-light.css";
@import "@prizm/tokens/c3-dark.css";
@import "@prizm/tokens/rc3-light.css";
@import "@prizm/tokens/rc3-dark.css";<div data-zone="c3" data-mode="dark" data-pack="rc3">
<YourRC3Surface />
</div>