Start with one command boundary in an isolated simulation. Prepare the interface catalog, one real message/goal example, the robot description, and the controller/configuration or calibration files relevant to that command. For a velocity topic, identify which node receives it.
No repository login, remote-machine access or cloud account is required. You review a separate workspace before running it. Setup time depends on whether your message semantics and configuration sources already fit; there is no measured customer setup-time estimate yet.
The installed CLI evaluates locally without a cloud connection and writes a readable report, per-check results and Evidence. This web page needs internet to load; the CLI, downloaded settings and installed documentation can be used offline after dependencies are installed. ROS graph discovery still uses local DDS traffic.
Choose one change together, such as a controller configuration or calibration copy. Keep the approved baseline unchanged, collect both observations, and compare them. Never change a live robot just to trigger a block.
WOULD_ALLOW means the declared authorization checks matched; it does not mean the motion is safe. Existing motor limits, readiness, emergency stops and collision checks remain in place. Public case studies, research plans and contribution credit need a separate agreement.
