production-readiness-audit

To audit application production readiness, run an evidence-backed evaluation across eight phases covering code quality, security, performance, reliability, observability, documentation, and deployment. It generates phase-level evidence files and synthesizes an overall READY, NOT READY, or CONDITIONAL verdict.

A production readiness audit systematically evaluates whether an application is safe and stable for deployment. You need one before an initial production rollout, a major release, or after significant refactors to validate deployment readiness with cited evidence.

To enforce blocking rules during a release readiness check, apply severity classifications that mark Phase 2 Security and Phase 7 Deployment failures as blocking. This automatically synthesizes a NOT READY verdict if critical security or deployment checks fail.

Yes, you can run a production readiness audit for web, backend, and service deployments after significant refactors. It validates code quality, security, performance, reliability, observability, and documentation to produce a defensible deployment decision.

Yes, a production readiness audit generates phase-level evidence files stored in structured e2e-evidence/prod-audit directories. It synthesizes these artifacts into a consolidated report to provide a defensible, evidence-backed deployment validation decision.

An automated production readiness audit is limited by its eight-phase scope, specifically classifying only Security and Deployment failures as blocking. Issues outside these phases may yield a CONDITIONAL verdict, requiring manual review to determine actual production stability.