Eve library

Isis Remediation Finding Ownership Matrix (F01-F22)

Guide

Revision 1

On this page

Date: 2026-02-21
Source: ISIS_TODOS.md, .github/CODEOWNERS

Purpose#

Define accountable ownership for every Isis remediation finding group (F01 through F22) using a team-level RACI model.

  • A (Accountable): Single owning team responsible for delivery.
  • R (Responsible): Teams executing work with the accountable owner.
  • C (Consulted): Teams that must be consulted before merge/release.
  • I (Informed): Teams notified of changes and rollout status.

Ownership Matrix#

Finding Scope A R C I
F01 Job submission to execution pipeline @oshun/isis-team @oshun/isis-team @oshun/platform, @oshun/ml-team @oshun/core-team
F02 Workflow catalog runtime integration @oshun/isis-team @oshun/isis-team, @oshun/ml-team @oshun/platform @oshun/core-team
F03 Canonical workflow schema and interop @oshun/isis-team @oshun/isis-team @oshun/ml-team, @oshun/docs-team @oshun/core-team
F04 Isis web app full feature exposure @oshun/isis-team @oshun/isis-team @oshun/security, @oshun/platform @oshun/core-team, @oshun/docs-team
F05 RunPod adapter productionization @oshun/ml-team @oshun/ml-team @oshun/isis-team, @oshun/platform @oshun/core-team
F06 RunPod handler capability expansion @oshun/ml-team @oshun/ml-team @oshun/isis-team @oshun/core-team
F07 Remove simulated runtime behavior @oshun/ml-team @oshun/ml-team @oshun/isis-team, @oshun/platform @oshun/core-team
F08 RunPod provisioning and drift control @oshun/devops @oshun/devops, @oshun/platform @oshun/ml-team, @oshun/isis-team @oshun/core-team
F09 Workflow registry persistence/auth hardening @oshun/isis-team @oshun/isis-team @oshun/security, @oshun/platform @oshun/core-team
F10 Output registry ownership/access control @oshun/isis-team @oshun/isis-team @oshun/security @oshun/core-team
F11 Health/readiness truthfulness @oshun/isis-team @oshun/isis-team, @oshun/platform @oshun/devops @oshun/core-team
F12 Model storage presign productionization @oshun/isis-team @oshun/isis-team @oshun/platform, @oshun/security @oshun/core-team
F13 Deployment configuration drift @oshun/devops @oshun/devops @oshun/isis-team, @oshun/platform @oshun/core-team
F14 Test coverage expansion for real execution @oshun/isis-team @oshun/isis-team, @oshun/ml-team @oshun/platform @oshun/core-team
F15 API and SDK contract parity @oshun/isis-team @oshun/isis-team @oshun/core-team, @oshun/docs-team @oshun/ml-team, @oshun/platform
F16 Security and multi-tenant hardening @oshun/security @oshun/security, @oshun/isis-team @oshun/core-team @oshun/platform, @oshun/devops
F17 Observability, cost, and SLOs @oshun/platform @oshun/platform, @oshun/isis-team @oshun/devops, @oshun/ml-team @oshun/core-team
F18 Data migration and backfill @oshun/isis-team @oshun/isis-team @oshun/platform, @oshun/devops @oshun/core-team
F19 Release plan and cutover @oshun/devops @oshun/devops, @oshun/isis-team @oshun/security, @oshun/platform, @oshun/ml-team @oshun/core-team
F20 Per-workflow E2E certification (45/45) @oshun/ml-team @oshun/ml-team, @oshun/isis-team @oshun/platform @oshun/core-team
F21 Interaction and user-journey coverage @oshun/isis-team @oshun/isis-team @oshun/security, @oshun/platform, @oshun/docs-team @oshun/core-team
F22 Operational resilience and compliance completion @oshun/devops @oshun/devops, @oshun/security, @oshun/platform @oshun/isis-team, @oshun/ml-team @oshun/core-team

Sign-Off Rules#

  • No finding can be marked done without approval from its A owner.
  • Findings with security impacts (F10, F16, F22) require @oshun/security explicit approval.
  • Findings with infrastructure/runtime costs (F05, F06, F08, F17, F19, F22) require @oshun/devops or @oshun/platform approval.
  • Findings that change public contracts (F15) require @oshun/docs-team docs parity sign-off.

Notes#

  • Ownership is team-level to align with repository CODEOWNERS and avoid person-specific churn.
  • If teams change, update this matrix and regenerate ticket assignments in remediation backlog artifacts.