Eve library

ISIS v2 Rollback and Change Freeze Policy

Guide

Revision 1

On this page

Date: 2026-02-23
Scope: M0 to M3 phases defined in docs/domains/isis/remediation-v2/ISIS_V2_MILESTONES.md

Purpose#

Define mandatory rollback triggers and change-freeze rules for each launch phase to reduce blast radius and preserve release integrity.

Global Rules#

  • Any triggered rollback condition pauses forward promotion immediately.
  • Incident commander (SRE) and owning function must be assigned within 30 minutes of trigger.
  • Rollback target must be latest verified stable state for the affected component.
  • Freeze windows block non-emergency changes unless exception approval is granted by Product + Platform + SRE.

Rollback Triggers (Global)#

Rollback is mandatory when any condition below occurs:

  1. Contract integrity failure in production path (API/SDK mismatch causing failed critical flows).
  2. Security regression with unresolved critical or high exploitability.
  3. Sustained SLO breach for critical flow beyond threshold for 30 minutes.
  4. Cost anomaly above approved threshold with no active mitigation.
  5. Data integrity regression (orphaned outputs, broken lineage/provenance writes in critical path).

Phase Policies#

M0 Foundation (2026-02-23 to 2026-04-03)#

Freeze Policy#

  • Freeze starts 48 hours before M0 gate decision.
  • Allowed during freeze:
    • blocker fixes for critical governance/contract issues,
    • documentation corrections for governance artifacts.
  • Disallowed during freeze:
    • schema shape changes without emergency waiver,
    • non-critical refactors.

Rollback Criteria#

  • Ticket generation artifacts lose 1:1 checklist mapping.
  • Severity/tagging/governance automation produces inconsistent output.
  • Missing required sign-off/rubric/milestone/acceptance artifacts.

M1 Expansion (2026-04-06 to 2026-05-29)#

Freeze Policy#

  • Freeze starts 72 hours before M1 gate decision.
  • Allowed during freeze:
    • runtime correctness fixes,
    • SRE-approved reliability patches.
  • Disallowed during freeze:
    • net-new runtime features,
    • provider topology redesign.

Rollback Criteria#

  • Provider/job execution path failures exceed approved threshold.
  • RunPod endpoint health degrades across critical families.
  • Cost attribution correctness falls below acceptance threshold.

M2 Certification (2026-06-01 to 2026-07-24)#

Freeze Policy#

  • Freeze starts 5 days before M2 gate decision.
  • Allowed during freeze:
    • test fixes with no behavior change,
    • critical accessibility/security remediations.
  • Disallowed during freeze:
    • UX redesign scope expansions,
    • non-critical dependency upgrades.

Rollback Criteria#

  • Certification suite fails for previously passing critical flows.
  • UX critical journeys regress.
  • Security or compliance checks fail for critical scenarios.

M3 Launch (2026-07-27 to 2026-10-30)#

Freeze Policy#

  • Progressive freeze:
    • soft freeze at start of M3,
    • hard freeze 7 days before launch close decision.
  • Allowed during hard freeze:
    • approved launch blockers only.
  • Disallowed during hard freeze:
    • new matrix scope additions,
    • architecture-level rework.

Rollback Criteria#

  • Launch gate sign-off is incomplete or revoked by any mandatory function.
  • Matrix certification evidence is incomplete or inconsistent.
  • Any production critical incident attributable to unresolved launch-scope changes.

Exception Process#

Freeze exceptions require:

  1. written risk statement,
  2. explicit rollback plan,
  3. approving signatures from Product + Platform + SRE.

Traceability#

Primary checklist item:

  • WS00-008

Related:

  • WS00-003
  • WS00-004
  • WS00-007