Runbooks

Operational runbooks tell operators what to do during bring-up, incidents, failures, drills, or recovery. Tutorials teach or validate expected behavior; runbooks are imperative procedures.

CE Operator Runbooks

For operators running the demo / CE-artifact stack on a single host or local cluster. Validates governed-tool behavior, supply-chain proofs, and failure drills without requiring a fleet topology or commercial agreement.

CE Operator Runbooks

• Demo Runbook
• ROS 2 Governed Bridge
• ROS 2 SROS 2 / DDS-Security for the Governed Bridge
• Container Hardening + Syscall Mediation
• Governed Python Runtime

Controlled Deployment Runbooks

For operators running the orchestrator-managed, partner/customer Controlled Deployment path: fleet rollout, HA, certificate management, RBAC, support-bundle collection, emergency rollback. “Controlled” denotes managed, auditable, partner/customer deployment with explicit operational controls — not a pricing tier.

Controlled Deployment Runbooks

• AutonomyOps Operator Runbooks
• Fleet Rollout Recovery
• Gate Approval Workflow
• Manual Failover Procedure
• Split-Brain Detection and Recovery
• Quorum-Loss Recovery
• Deadletter Inspection and Retry Workflow
• Bandwidth Troubleshooting
• RBAC Role Assignment
• Support Bundle Generation
• Emergency Rollback Procedure
• Attestation Mode Rollout

Developer Runbooks

In-repo / engineering runbooks for failure-injection harness debug flows and integration-test integrity drills. These pages assume a git clone checkout and the in-repo build toolchain (make fi, make fi-root, registry+cosign). They are not part of the operator-under-fire path — operators following the install flow should use the CE or Controlled runbooks above.

Developer Runbooks

• Operator Runbook
• Integrity Failure Drill: Tamper and Verify Failure

The certificate rotation procedure for orchestrator operators is published in the self-hosted tier: see the self-hosted tier site.