Each entry maps a hardware archetype or manifest signal to a published Python package
and (when shipped) a Claude Code plugin. Search from the CLI:
robot-md actuator search "raspberry pi camera".
robot-md actuator publish from your package directory.
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.