# Isis Release Train Cadence Policy Runbook

Last Updated: 2026-02-24  
Scope: WS18-005 release cadence, freeze windows, and hotfix governance.

## Purpose

Define and maintain a deterministic Isis release train with:

1. Fixed weekly stage cadence
2. Explicit freeze windows
3. Emergency hotfix approval and verification policy

## Artifacts

- `docs/domains/isis/remediation-v2/ISIS_V2_RELEASE_TRAIN_CADENCE_POLICY.json`
- `docs/domains/isis/remediation-v2/ISIS_V2_RELEASE_TRAIN_CADENCE_POLICY.md`

## Generator

```bash
node scripts/isis/generate-v2-release-train-cadence-policy.mjs
```

## Validator

```bash
node scripts/isis/validate-v2-release-train-cadence-policy.mjs
```

## Operational Use

1. Run generator and validator when release stage timing, freeze windows, or
   hotfix approval rules change.
2. Treat freeze windows as blocking for non-hotfix production changes.
3. Allow freeze bypass only per policy severity rules (`p0`/`p1`).
4. Require listed automation checks before train progression and after hotfix
   deployment.
5. Attach generated cadence policy artifacts to release governance packets.

## Related Artifacts

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