harness:canary

Generate a structured canary deployment runbook by extracting git diff context to compute a numeric risk score, planning 2-to-5 stage traffic rollout percentages, and defining automated rollback triggers for production rollouts.

A canary deployment runbook is a structured pre-deployment plan that reduces production incidents by defining risk-based traffic stages, rollback procedures, and observability checks for releases involving migrations, payments, or security changes.

Compute a numeric risk score for canary releases by evaluating explicit dimensions including data sensitivity, security blast radius, change novelty, and reversibility signals extracted from your git diff and log context.

Define automated rollback conditions tied to quantitative error and latency thresholds, and generate an observability checklist with dashboards, log queries, and post-deploy smoke tests to verify business metrics during the canary rollout.

Yes, the generated deployment runbook inserts a mandatory human confirmation gate before deployment, ensuring you review the risk score, canary stages, and rollback plan without initiating any automated production rollout.

Risk-based canary staging applies to changes involving database migrations, authentication or security updates, payment systems, new environments or regions, and any production-impact changes requiring explicit deployment checklists.