From the pack / Product notes
Leash: keep the agent separate from device authority
A language model can propose an action. A robotics runtime must decide whether that action is allowed to reach a device. Leash keeps that boundary explicit.
A different product, a different responsibility
Leash is a Rust robotics runtime with CLI, HTTP and MCP interfaces. Its current documentation describes simulation/replay, typed telemetry, bounded navigation, scoped agent capabilities and feature-gated hardware adapters.
This is separate from Dotdog's spec/code graph tooling. Dotdog's optional type and REA workflows do not require robotics, a simulator, sensors or a provisioned cloud account.
One control boundary
Leash's documented architecture routes requests through the runtime before a robot adapter receives a command. Planners, ROS 2 providers, model outputs and CUDA results supply requests or evidence; they do not become an additional motor writer.
Depending on the physical operation, the documented checks include authorization, approval, ownership, freshness, deadman state, collision/distance limits, Stop and E-stop. Those are implementation boundaries to inspect and test, not a blanket certification that a robot is safe in every environment.
Start without hardware
The project's simulation entry points let a developer inspect command/telemetry behavior without actuating a physical robot. Follow the current quickstart and distinguish a simulation result from hardware evidence.
Record the runtime revision, configuration, inputs and observed stop behavior when evaluating a workflow. A replay that matches a recorded run is useful evidence about that case, not proof of every future physical condition.
Types help connect the pieces
Typed control and sensor contracts make units, states and expected fields explicit. Runtime checks are still required for stale observations, authorization and device faults. This is the same separation used in type-driven software development: representable states, runtime input checks and behavioral evidence each do different work.
What this article does not claim
This is a source-backed product overview, not a new hardware trial, field certification or reproduction of every ROS/CUDA configuration. Consult the repository's actual adapter-specific evidence before making a physical-deployment decision.