Date: 2026-02-22
Checklist Item: REL-006
Ticket: ISIS-0180
Purpose#
Define the mandatory post-cutover validation sequence and evidence requirements before declaring Isis full production cutover complete.
Required Inputs#
- Release identifier and deployment timestamp
- Game-day evidence report (
REL-005) - Rollback owner and rollback command pathway
- Access to Isis API operational endpoints
- Access to canary/cost telemetry data store
Automated Validation Run#
Run the post-cutover harness immediately after promotion:
bash
ISIS_API_BASE_URL=https://<isis-api-host> \
ISIS_DATABASE_URL=postgres://... \
STRICT=true \
scripts/isis/run_post_cutover_validation.sh
Primary output artifact:
tmp/isis-cutover/post-cutover-validation-<timestamp>.json
Checklist#
0-15 Minutes (Immediate)#
-
/healthreturns HTTP 200 -
/readyreturns HTTP 200 - queue feature flags match full cutover expectation:
queue.producerEnabled=true- canary disabled (
enabled=false,percentage=0) unless explicitly waived
- RunPod operations snapshot captured
- rollback owner confirms rollback path remains executable
15-60 Minutes (Stabilization)#
- post-cutover SLO/cost guardrail report generated
- no blocking fail checks in post-cutover validation report
- queue/provider drift check completed (if enabled)
- incident channel shows no unresolved P0/P1 trigger
1-24 Hours (Confidence)#
- game-day evidence is attached to cutover packet
- open failed checks have owner + remediation ticket + due date
- security sign-off confirms no new high/critical regression
- platform sign-off confirms cost/runtime completeness health
Mandatory Evidence Artifacts#
- Post-cutover validation harness report JSON.
- Game-day report + scenario outcomes.
- Canary SLO/cost verification report.
- Ramp/rollback decision report from latest ramp phase.
- Completed sign-off record:
docs/domains/isis/remediation/ISIS_CUTOVER_SIGNOFF_TEMPLATE.md
Failure Handling#
If any mandatory check fails:
- Mark cutover state as
HOLD. - Evaluate rollback criteria in:
docs/domains/isis/remediation/ISIS_ROLLBACK_CRITERIA.md
- Execute rollback if trigger conditions are met.
- Create remediation tasks and update owners before re-attempting sign-off.
Exit Condition#
Post-cutover validation is complete only when:
- all mandatory checks pass or approved waiver is documented,
- all blocking sign-offs are recorded,
- final decision is explicitly logged as
GO.
Traceability#
REL-006: Finalize post-cutover validation checklist and sign-off- Related:
docs/domains/isis/remediation/ISIS_RELEASE_QUALITY_BAR.mddocs/domains/isis/remediation/ISIS_GAMEDAY_CUTOVER_PLAN.mddocs/domains/isis/remediation/ISIS_CUTOVER_SIGNOFF_TEMPLATE.md