Eve library

ISIS Severity Rubric v2

Guide

Revision 1

On this page

Date: 2026-02-23
Source Checklist: ISIS_TODOS_2.md
Scope: Gap severity classification for v2 remediation tasks and generated ticket artifacts.

Purpose#

Define a consistent severity model (critical, high, medium, low) for all v2 remediation tasks so scheduling, escalation, and reporting remain deterministic.

Severity Levels#

Severity Definition Delivery Expectation Escalation
critical Failure blocks core platform correctness, contract integrity, or release governance for full v2 completion. Must be prioritized immediately in current phase plan. Escalate to @oshun/core-team same business day.
high Failure materially degrades production capability for runtime, serverless operations, security, or creator UX parity. Prioritize within active milestone; no carryover without explicit waiver. Escalate to owning functional lead within 24h.
medium Failure limits certification depth, operational maturity, or completeness polish but does not block foundational correctness. Schedule in planned phase and track burn-down weekly. Escalate during weekly program review if blocked > 5 business days.
low Failure impacts non-blocking package breadth or optimization-level completeness. Batch and execute after higher severities within same phase boundaries. Escalate only when accumulation risks milestone slip.

Mapping Rules Applied to ISIS_TODOS_2.md#

Severity tags are assigned deterministically in scripts/isis/generate-remediation-backlog-v2.mjs:

  • critical:
    • Global DoD checklist items (DOD2-*)
    • WS00 to WS03
    • WS10
  • high:
    • WS04 to WS13
    • Matrix workstreams MXB, MXC
  • medium:
    • WS14 to WS18
    • Matrix workstream MXA
  • low:
    • Matrix workstream MXD

Task Tagging Requirements#

Every generated v2 ticket must include:

  • priority:<P0|P1|P2>
  • severity:<critical|high|medium|low>
  • workstream:<...>

These tags are emitted into:

  • docs/domains/isis/remediation-v2/ISIS_REMEDIATION_V2_TICKETS.json
  • docs/domains/isis/remediation-v2/ISIS_REMEDIATION_V2_TICKETS.csv
  • docs/domains/isis/remediation-v2/ISIS_REMEDIATION_V2_BACKLOG.md

Validation Rule#

Regeneration is required after any checklist status/structure change:

bash
node scripts/isis/generate-remediation-backlog-v2.mjs

Validation is successful when:

  1. Ticket count remains 1:1 with checklist checkboxes.
  2. Every ticket has a severity tag.
  3. Duplicate checklist IDs are zero in ISIS_REMEDIATION_V2_SUMMARY.json.