ROBOTICS: FROM INTENT TO MOTION.

Start with the command boundary: what a caller is asking for, which units and frames describe it, and how a result will be reported. The robotics collection builds that foundation without assuming that a browser illustration is a controller.

Read the beginner’s guide first for a vocabulary of commands, capabilities, and state. Follow it with the coordinate frames article when a pose crosses camera, tool, and base boundaries. The simulation test plan then turns those assumptions into repeatable checks for rejected inputs, stale context, and recovery.

These guides focus on design reasoning rather than a particular robot brand. Physical implementations require the chosen controller’s documentation and an application-specific engineering process. The Robot Arm API overview connects the articles to a layered architecture, while the local playground gives you a deliberately small state interface to inspect. Use the reference to see exactly where that demonstration’s contract ends.