Eve library

Isis Remediation Milestones (Phased Schedule)

Guide

Revision 1

On this page

Date: 2026-02-21
Source: ISIS_TODOS.md, docs/domains/isis/remediation/ISIS_REMEDIATION_TICKETS.json

Goal#

Define explicit target dates for Phase 0/1/2/3 and establish gate-based progression criteria.

Milestone Plan#

Milestone Phase Start Date End Date Focus
M0 Foundation Phase 0 2026-02-23 2026-03-20 Program setup and P0 execution blockers (WS00, F01, F02, F03, F04, F15)
M1 RunPod Productionization Phase 1 2026-03-23 2026-04-17 Provider/runtime productionization (F05, F06, F07, F08)
M2 Hardening and Parity Phase 2 2026-04-20 2026-05-22 Persistence, security, contract and test hardening (F09–F14, F16, F17, F18, parity items)
M3 Certification and Operational Closure Phase 3 2026-05-25 2026-06-26 Full certification, journey coverage, cutover and ops completion (F19, F20, F21, F22, gates)

Phase Gates#

Gate M0 -> M1 (2026-03-20)#

  • All WS00 tickets complete.
  • All F01/F02/F03 tickets complete.
  • Generation pipeline transitions jobs from submit to real execution.
  • Canonical workflow schema agreed and enforced.

Gate M1 -> M2 (2026-04-17)#

  • All F05/F06/F07/F08 tickets complete.
  • RunPod adapter no longer relies on placeholder cost/history functionality.
  • Infrastructure drift detection and reconcile workflow operational.

Gate M2 -> M3 (2026-05-22)#

  • All F09–F14, F16, F17, F18 tickets complete.
  • API/SDK parity checks pass in CI.
  • Security and readiness checks are production-truthful and verified.

Final Close (2026-06-26)#

  • All WF-*, UX-*, OPS-*, GATE-* tickets complete.
  • 45/45 workflow certifications complete.
  • Web app parity complete across all required interactions.
  • Production cutover sign-off complete.

Tracking Rules#

  • Every ticket in ISIS_REMEDIATION_TICKETS.json must have a milestone value.
  • Any date changes require updating this file and regenerating ticket artifacts.
  • No phase may start execution before the previous phase gate criteria are satisfied.