# ISIS v2 Release Train Cadence Policy

Generated: 2026-02-24T20:22:08.116Z Version: 1.0.0 Timezone: UTC

## Release Train Stages

| Stage                        | Day       | Start (UTC) | Duration (min) | Objective                                                             |
| ---------------------------- | --------- | ----------- | -------------- | --------------------------------------------------------------------- |
| stage-1-branch-cut           | Tuesday   | 18:00       | 90             | Create release branch and lock scope to approved tickets only.        |
| stage-2-candidate-validation | Wednesday | 18:00       | 180            | Validate release candidate with quality gates and rollback readiness. |
| stage-3-canary-promotion     | Thursday  | 17:00       | 240            | Promote to canary cohort and monitor for rollback triggers.           |
| stage-4-ramp-or-hold         | Friday    | 17:00       | 180            | Ramp to broader traffic or hold based on gate outputs.                |

## Freeze Windows

### freeze-weekend-change-freeze

- Type: recurring
- Window: Friday 20:00 -> Monday 14:00
- Applies To: standard-release, canary-ramp, schema-change
- Allowed Exceptions: p0-hotfix, p1-hotfix-approved
- Rationale: Protects reduced-support windows and avoids uncontrolled weekend
  blast-radius expansion.

### freeze-milestone-cutover-protection

- Type: fixed
- Window: 2026-06-24T00:00:00Z -> 2026-06-27T00:00:00Z
- Applies To: all-non-hotfix-production-changes
- Allowed Exceptions: p0-hotfix, security-emergency-hotfix
- Rationale: Enforces launch cutover stability near M3 close with only emergency
  hotfix exceptions.

## Hotfix Severity Rules

| Severity | Freeze Bypass | Max Mitigation (min) | Approval Roles                                     |
| -------- | ------------- | -------------------- | -------------------------------------------------- |
| P0       | true          | 30                   | incident-commander, service-owner                  |
| P1       | true          | 60                   | incident-commander, release-manager, service-owner |
| P2       | false         | 240                  | release-manager                                    |

## Automation Checks

### Pre-Train

- `check-launch-readiness`: `scripts/isis/run_launch_readiness_checklist.sh` ->
  `tmp/isis-launch/launch-readiness-*.json`
- `check-release-failure-scenarios`:
  `scripts/isis/run_release_failure_gameday.sh` ->
  `tmp/isis-release-failure-gameday/release-failure-gameday-*.json`
- `check-oncall-triage`: `scripts/isis/run_creative_pipeline_oncall_triage.sh`
  -> `tmp/isis-oncall/creative-pipeline-oncall-triage-*.json`

### Hotfix Verification

- `check-canary-slo-cost`: `scripts/isis/verify_canary_slo_cost.sh` ->
  `tmp/isis-canary/canary-slo-cost-report-*.json`
- `check-ramp-decision`: `scripts/isis/advance_queue_canary_rollout.sh` ->
  `tmp/isis-canary/canary-rollout-decision-*.json`
- `check-post-cutover`: `scripts/isis/run_post_cutover_validation.sh` ->
  `tmp/isis-cutover/post-cutover-validation-*.json`

## References

- `docs/domains/isis/remediation/ISIS_RELEASE_QUALITY_BAR.md`
- `docs/domains/isis/remediation/ISIS_ROLLBACK_CRITERIA.md`
- `docs/domains/isis/remediation/ISIS_SLO_DEFINITIONS.md`
- `docs/domains/isis/runbooks/runpod-oncall.md`
- `docs/domains/isis/runbooks/creative-pipeline-oncall.md`
