Category 9 of 10
Deploy and rollback
Production changes come from one reviewed path and can be undone within a known time.
v1.0 · verified on 2026-09-21
One reviewed path to production, and a rollback that has been timed this month.
Production deploys are triggered only from the reviewed branch in CI
manual Read the deployment configuration and the last 10 production deploy records.
Every production deploy in the sample originates from CI on the protected branch; no local push or agent session deployed to production.
Rollback rehearsed on the previous release
manual Roll the staging environment back one release, including any data migration, and time it.
Rollback completes within the written target time and the smoke suite passes on the rolled-back build.
Agents and tools hold no write credentials to production
manual Inventory every credential available to coding agents, CI jobs and developer machines.
No agent or developer session credential can write to production data or trigger a production deploy without a human approval step.
Environment configuration matches across staging and production
automated Diff the set of variable names and feature flags between staging and production.
The only differences are values, not names; every flag present in one exists in the other.
Release notes carry the checklist version and verdict
manual Open the release record.
The record names the checklist version, the verdict, the build hash and the tester.
Dots: Starter, Growth, Scale. Compare plan limits.
Failure patterns these items catch
- criticalCoding agent holds production credentials
An agent session can run commands against production data or infrastructure without a human approval step.
- highProduction deploy from a local push
Anyone with the CLI or a hosting token can deploy to production without review.
- highRollback never rehearsed
The team believes it can roll back but has not done it, and finds out the migration or the cache makes it slow or impossible.
- mediumStaging and production configured differently
A flag or variable exists in one environment and not the other, so a release passes in staging and fails in production.
Ask which plan runs these items
Email with your team size, cadence and stacks. We reply within 24 hours on business days.