Eve library

Isis Remediation v2 Milestones

Guide

Revision 1

On this page

Date: 2026-02-23
Source: ISIS_TODOS_2.md, docs/domains/isis/remediation-v2/ISIS_REMEDIATION_V2_TICKETS.json

Goal#

Define hard milestone dates for v2 delivery phases: Foundation, Expansion, Certification, and Launch.

Milestone Plan#

Milestone Date Range Scope
M0 Foundation 2026-02-23 to 2026-04-03 Governance and foundational contract work (WS00 to WS03 + DoD alignment).
M1 Expansion 2026-04-06 to 2026-05-29 Runtime/serverless/platform capability expansion (WS04 to WS10).
M2 Certification 2026-06-01 to 2026-07-24 UX, reliability, security, and operational closure (WS11 to WS18).
M3 Launch 2026-07-27 to 2026-10-30 Matrix-scale certification and launch-readiness closure (MXA, MXB, MXC, MXD).

Gate Criteria#

Gate M0 -> M1 (target: 2026-04-03)#

  • All WS00-*, WS01-*, WS02-*, and WS03-* tasks are complete.
  • V2 remediation artifacts regenerate cleanly with 1:1 ticket linkage.
  • Severity rubric and sign-off matrix are active and referenced in governance.

Gate M1 -> M2 (target: 2026-05-29)#

  • All WS04-* through WS10-* tasks are complete.
  • Runtime, RunPod, and external integration capabilities meet defined acceptance criteria.
  • No unresolved critical severity item remains in M1 scope.

Gate M2 -> M3 (target: 2026-07-24)#

  • All WS11-* through WS18-* tasks are complete.
  • Cross-functional sign-offs are complete for Certification gate.
  • Quality, reliability, security, and operational checks pass.

Final Launch Close (target: 2026-10-30)#

  • Matrix scope (MXA-*, MXB-*, MXC-*, MXD-*) is fully completed and certified.
  • Launch gate sign-offs complete across Product, Platform, Creative Tech, Frontend, SRE, and Security.
  • Final executive closure report published.

Tracking Rules#

  • Milestone dates are fixed unless changed through program governance approval.
  • Ticket milestone fields are generated from scripts/isis/generate-remediation-backlog-v2.mjs and must not be edited manually in generated files.
  • Any milestone change requires regenerating v2 ticket artifacts.

Traceability#

Primary checklist item:

  • WS00-004

Related tasks:

  • WS00-003
  • WS00-005
  • WS00-006