# ISIS v2 Sign-Off Matrix

Date: 2026-02-23  
Scope: Cross-functional approval model for `ISIS_TODOS_2.md` remediation
execution and release decisions.

## Purpose

Define mandatory approvers, evidence requirements, and blocking criteria for the
v2 remediation program so completion decisions are consistent and auditable.

## Required Functions

- Platform
- Creative Tech
- Frontend
- SRE
- Security
- Product

## Approval Gates

| Gate | Description                                                    | Required Sign-Offs                         |
| ---- | -------------------------------------------------------------- | ------------------------------------------ |
| `G0` | Program governance setup complete (`WS00-*`)                   | Product, Platform                          |
| `G1` | Contract and taxonomy foundations complete (`WS01-WS03`)       | Platform, Creative Tech, Security          |
| `G2` | Runtime and RunPod capability expansion complete (`WS04-WS10`) | Platform, Creative Tech, SRE, Security     |
| `G3` | UX and operational readiness complete (`WS11-WS18`)            | Frontend, Product, SRE, Security           |
| `G4` | Matrix-scale certification closure (`MXA-MXD`)                 | Creative Tech, Frontend, Platform, Product |

No gate is considered complete unless every required function signs off.

## Function Ownership and Criteria

| Function      | Primary Owner          | Delegates Allowed               | Mandatory Evidence                                                                     | Block Conditions                                                       |
| ------------- | ---------------------- | ------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Platform      | `@oshun/platform`      | `@oshun/isis-team` tech lead    | Contract parity checks, observability health, queue/provider readiness                 | Missing telemetry, unresolved contract drift, failed reliability gates |
| Creative Tech | `@oshun/creative-tech` | domain leads for asset families | Workflow coverage matrix, control/consistency certification, quality benchmark results | Uncovered asset/control classes, failed consistency thresholds         |
| Frontend      | `@oshun/isis-web`      | design system lead              | UX parity tests, accessibility checks, creator/reviewer workflow validation            | Broken UX journeys, inaccessible critical interactions                 |
| SRE           | `@oshun/devops`        | on-call lead                    | RunPod endpoint health, rollout/rollback readiness, SLO reports                        | Failed canary/ramp criteria, missing rollback readiness                |
| Security      | `@oshun/security`      | security reviewer on duty       | Authz and tenant isolation checks, callback signing verification, policy conformance   | Critical/high unresolved findings, tenant boundary regression          |
| Product       | `@oshun/product`       | product ops lead                | Scope acceptance, user-priority alignment, release readiness summary                   | Scope misses high-priority features, unresolved acceptance criteria    |

## Sign-Off Workflow

1. Delivery owner prepares an evidence bundle for the target gate.
2. Evidence bundle is posted with references to tickets and artifacts.
3. Each required function records one of: `APPROVED`,
   `APPROVED_WITH_CONDITIONS`, `REJECTED`.
4. `APPROVED_WITH_CONDITIONS` requires deadline-bound follow-up tickets.
5. Any `REJECTED` status blocks gate completion.
6. Product records final gate disposition after all mandatory approvals.

## Evidence Bundle Minimum Contents

- Gate target and included checklist IDs.
- Summary of completed tickets and remaining risks.
- Test results (contract, integration, E2E, reliability, security).
- Operational data (RunPod metrics, queue health, cost/compliance signals).
- UX validation artifacts for relevant creator/reviewer/operator flows.
- Exception list (if any) with owner and remediation deadlines.

## Decision Record Template

```md
### ISIS v2 Gate Sign-Off

- Gate:
- Date:
- Scope (ticket ranges):
- Evidence bundle:
- Platform:
- Creative Tech:
- Frontend:
- SRE:
- Security:
- Product:
- Result: APPROVED | APPROVED_WITH_CONDITIONS | REJECTED
- Conditions (if any):
- Follow-up tickets:
```

## Traceability

Primary checklist item:

- `WS00-003`

Related governance tasks:

- `WS00-004`
- `WS00-005`
- `WS00-006`
- `WS00-007`
