Track 3 — PROVISIONAL
Bob — SO-ARM101
RPN-000000000002 dispatched end-to-end on a Raspberry Pi 5 with 5 signed evidence records covering bypass-denial, gated motion, replay defense, and 100-iteration 6-joint range-of-motion fidelity.
Each case study documents one operator wiring a real robot through the OpenCastor / RobotRegistryFoundation stack — package, registration and signed evidence — with IDs you can verify yourself.
Where safety is meant to be enforced.
Physical limits are meant to be enforced at Layer 3 (robot-md-gatewayand the actuator driver it calls), and only for commands that pass through it. OpenCastor (Layer 4) does not embed the gateway yet, so actuators it drives directly are not covered. Declaration alone (Layer 1) does not enforce safety. Agent host alone (Layer 2) is not the safety boundary. If a deployment lacks Layer 3, no safety claim attaches to it. Layer 3 is not a certified safety function, and hostile-input testing in simulation (October 2026) found motions it does not yet bound.