Documented step-by-step rollback procedure covering code, database, and infrastructure

A bad production deployment without a documented rollback plan means your team is improvising under pressure during an outage — when clarity matters most. Database schema changes and infrastructure shifts cannot be undone by git revert alone. Without step-by-step rollback coverage for code, database, and infrastructure (SOC 2 A1.3, NIST CP-10), teams routinely extend incidents from minutes to hours. ISO 25010 reliability.recoverability requires demonstrable recovery procedures, not tribal knowledge.

Create DEPLOYMENT.md or RUNBOOK.md at the repo root with explicit steps for reverting code, database migrations, and infrastructure changes.

# Rollback Procedure

## Code Rollback (~5 minutes)
1. Identify the previous stable tag or commit hash
2. Redeploy: `git revert <bad-commit>` then push, or trigger re-deploy from prior tag
3. Verify health check at `/api/health` returns 200

## Database Rollback (~15 minutes)
1. Run: `npx prisma migrate resolve --rolled-back <migration-name>`
2. Restore from backup snapshot taken at deployment time if schema is incompatible
3. Confirm critical queries return expected data

## Infrastructure Rollback (~20 minutes)
1. Revert IaC change: `terraform apply -target=<resource>`
2. Confirm routing and load balancer state

Include estimated times — they set expectations during an active incident.