Documentation is coming.
The outline below is the shape it will take. Nothing here is written yet — we'd rather show the skeleton than publish filler.
What you need locally: a container runtime, a Python environment, and a robot description.
Point Vesk at a robot description, describe what the robot should do, and read the run.
Events, attempts, and how to tell a verified result from an advisory one.
What gets asserted, and why it is generated alongside the node rather than after it.
Build error, crash, assertion, timeout, vacuous — and what each one sends back to the fix loop.
Why a run reports what it could not check, and what that blocks.
Physical simulation scoring, and why it never gates a verdict.
Links, joints, actuated joints, and the naming rules that make a model importable.
ROS 2 Jazzy and MuJoCo. No Gazebo layer yet.
Want a specific page first? Tell us on the waitlist.