ops-patrol

Ops status routing consolidates local truth sources like lock ledgers, release journals, and health checks to provide a reliable, auditable status view. It reads these sources to diagnose health and incidents without executing privileged operations.

Run the ops-patrol status command to fetch the latest truth sources. The system routes deploy-now, rollback, and version actions through mirise-cli, providing a safe, auditable decision-support workflow for operations teams.

Yes, you can automate incident management and health diagnostics within DevOps pipelines. The system reads local run states and maintenance windows to diagnose incidents and route actions safely, flagging missing or degraded data for operational safety.

No, ops-patrol does not require direct execution privileges. It routes actions through mirise-cli without executing privileged operations itself, ensuring a safe decision-support workflow that flags missing or degraded data for safety.

When operational truth sources like VM audits or run states are missing or degraded, the system flags these data issues for safety. This prevents unreliable automated decisions by ensuring the auditable status view remains accurate before routing actions.

A unified ops patrol approach provides a single auditable status view by consolidating multiple operational truth sources. Unlike separate tools, it safely diagnoses health and routes actions across incidents, deployments, and rollbacks without executing privileged operations.