autonomy ros2

Execute governed ROS2 commands under AutonomyOps policy

Synopsis

Execute ROS2 commands under AutonomyOps policy governance.

All subcommands dispatch through the dual-path executor:

  Container path (default when Docker is available):
    ROS2 runs inside an OCI container with full policy interception and
    container isolation.  Requires --image to be set to a ROS2-capable image.

  Native path (fallback when Docker is absent):
    ROS2 runs as a native subprocess with no container isolation and no active
    interception layer — REDUCED-GOVERNANCE. This path is FAIL-CLOSED by
    default: it is refused unless you explicitly pass
    --allow-reduced-governance (the acceptance is logged and audited). The
    container path is the only fully-governed path; use it for production.

  Neither available:
    Returns an error if Docker is absent and ros2 is not in PATH.

Options inherited from parent commands

      --require-signed-manifest   Refuse to start if the SHA256SUMS release manifest or its cosign signature is missing/invalid (Tier 2 binary-integrity check; default: build-time compile-in via -ldflags -X, build-hardened artifacts=true, all others=false)

Subcommands

• autonomy ros2 bridge — Manage the governed_ros2_bridge native binary

• autonomy ros2 doctor — Diagnose common SROS 2 secured-graph misconfigurations (version skew, keystore, transport) before they fail silently

• autonomy ros2 keystore — Manage SROS 2 keystores for the governed bridge (#938 Phase 3-A)

• autonomy ros2 run — Run a ros2 subcommand under policy governance (dual-path)

• autonomy ros2 secure-env — Print the SROS 2 env a node needs to join the secured graph (after verifying keystore + enclave)

• autonomy ros2 secure-run — Verify the keystore + enclave, then run a command with the SROS 2 env injected