Approval-first execution
Production actions remain gated until a human reviews the evidence packet and approves the proposed runbook step.
Security
Security centered on proof and approval.
RunProof keeps investigation, recommendation, and execution separated so automation can assist without silently taking control.
Evidence visibility
RunProof keeps the supporting logs, traces, metrics, sandbox output, and decision history visible so reviewers can understand the recommendation.
Sandbox diagnostics
Diagnostics are designed to run outside production first, reducing the chance that investigation work becomes an operational change.
Least privilege
Deployments should grant the application only the permissions required for the configured runbooks, data sources, and approval workflow.
Audit trail
Run decisions are recorded with context so teams can review what was proposed, what was approved, and when the gate changed state.
Report an issue
Security concerns should be reported through the repository or the disclosure process configured by the team operating this deployment.