mh-cto-sdlc-prod-readiness

Production readiness verification requires reviewing observability specifications and resilience surface maps to confirm monitoring, alerting, runbooks, rollback procedures, and data protection measures are fully operational.

A production readiness review checks that monitoring and alerting systems are operational, runbooks are accessible for critical failure modes, and incident response paths define on-call rotation, severity classification, and response SLAs.

Testing rollback procedures involves verifying the tested rollback plan prevents system failure, while data protection verification checks database backups, encryption at rest, secret rotation, and environment variable handling.

Performing a production system readiness check requires reviewing observability specifications, resilience surface maps, and other technical documents to validate monitoring, alerting, and incident response paths.

The best way to ensure runbooks and communication channels are ready is to verify runbooks are written and reviewed for critical failure modes and incident response paths define communication channels and post-incident review processes.

No external dependencies are required for the production readiness verification process, which relies on reviewing technical documents like observability specifications and resilience surface maps to validate system readiness.