Skip to main content

Promote a release to production

This playbook covers the end-to-end production promotion flow.

Steps​

  1. Goal reaches READY_FOR_RELEASE.
  2. Orchestrator emits a MERGE_APPROVAL gate.
  3. Owner submits an approving GitHub review at the exact PR head.
  4. Orchestrator ingests the review → gate materialized.
  5. Orchestrator re-runs and consumes the gate.
  6. Governed merge happens.
  7. CI on main re-runs.
  8. Orchestrator emits a PRODUCTION_PROMOTION gate.
  9. Owner signs the production ticket offline.
  10. Owner submits the ticket to the orchestrator.
  11. Orchestrator verifies the ticket with ssh-keygen -Y verify.
  12. Orchestrator consumes the gate.
  13. Production target pulls the release artifact.
  14. Orchestrator transitions the goal to FROZEN_PASS.
  15. evidence/<GOAL_ID>/deployment_health.txt is written.

What this playbook is NOT​

  • It does not click Merge from chat.
  • It does not push to main directly.
  • It does not edit the runtime DB.
  • It does not skip the GitHub review.