Release Health Gates

When NOT To Use

• Measuring delivery performance (use minister:dora-metrics)
• PR-level quality gates before merge (use sanctum:pr-prep)

Purpose

Standardize release approvals by expressing gates as GitHub-aware checklists. Ensure code, docs, comms, and observability items are green before deployment.

Gate Categories

1. Scope & Risk – Are all blocking issues closed or deferred with owners?
2. Quality Signals – Are required checks, tests, and soak times satisfied?
3. Comms & Docs – Are docs merged and release notes posted?
4. Operations – Are runbooks, oncall sign-off, and rollback plans ready?

Workflow