he-verify-release

Release readiness verification checks test evidence, invariant conditions, and rollback feasibility to produce a documented go/no-go decision. This process ensures all review gates pass and evidence for user-visible changes is captured before deployment proceeds.

A go/no-go decision is a formal release gate determination recorded in the active plan based on test pass rates, architectural invariants, and security review status. It escalates uncertainty by requiring explicit rollback procedures before approving deployment.

Rollback feasibility is checked by verifying that rollback procedures are explicit, documented, and actionable within the active plan. This ensures that if deployment issues arise, the rollback steps have been validated prior to execution.

Evidence collection for user-visible changes gathers and records artifacts, including agentic end-to-end test results. This documentation proves that critical gates passed and validates the release candidate's behavior before the final deployment decision.

When architectural invariants fail verification, the release process escalates the uncertainty and records a no-go decision. This prevents deployment by ensuring all critical architectural rules and security reviews pass before proceeding.

Release verification independently automates checks for test pass rates, architectural invariants, and security review status. It aggregates these results to formally record a deployment decision, ensuring no gate is manually skipped.