Production Readiness¶
Purpose: decide whether the team is comfortable owning the system after users rely on it.
Use this section by itself when launch evidence, accepted risks, support ownership, escalation, and post-launch review need a gate.
Inputs¶
- Product readiness evidence.
- Data readiness evidence.
- Security readiness evidence.
- Quality readiness evidence.
- Operations readiness evidence.
- Business readiness evidence.
- Accepted risks.
Outputs¶
- Production readiness score.
- Local launch decision inputs.
- Accepted risks.
- Runbook.
- Post-launch review plan.
Agent Task Contract¶
Help the reader summarize readiness by domain, identify blockers, and name missing evidence. Do not approve launch, compliance, security acceptance, or production release.