# ISIS v2 Immutable Acceptance Criteria

Date: 2026-02-23  
Source Checklist: `ISIS_TODOS_2.md`

## Purpose

Define immutable, testable acceptance criteria for:

1. Full Comfy workflow-class coverage.
2. Complete UI interaction exposure.

These criteria are release-blocking and may not be waived without documented
program-level exception approval.

## A. Workflow-Class Coverage Criteria

A release candidate passes workflow coverage only when all conditions below are
true.

### A1. Class Coverage Inventory

- A canonical workflow-class inventory exists and is versioned.
- Every workflow class in scope has at least:
  - one baseline workflow,
  - one controlled/conditioned variant,
  - one consistency-locked variant (where applicable).

### A2. Contract Coverage

- Every workflow class has:
  - schema-valid input contract,
  - schema-valid output package contract,
  - provider compatibility declaration,
  - model/custom-node dependency manifest.

### A3. Execution Coverage

- Every workflow class has at least one passing end-to-end execution test
  across:
  - API submission,
  - queue dispatch,
  - provider execution,
  - output registration,
  - provenance/lineage write.

### A4. Consistency and Control Coverage

- Applicable workflow classes expose required control modalities and consistency
  strategies.
- Drift/consistency benchmarks exist with explicit thresholds and pass/fail
  evidence.

### A5. Certification Coverage

- Every workflow class has a certification artifact with:
  - test evidence links,
  - quality benchmark results,
  - unresolved risk status,
  - certifier sign-off.

## B. UI Interaction Coverage Criteria

A release candidate passes UI coverage only when all conditions below are true.

### B1. Route and Screen Coverage

- Every API capability in scope has a discoverable UI route/screen mapping.
- Route-to-capability matrix reports 0 unmapped capabilities.

### B2. Interaction Completeness

- For each workflow class, UI supports:
  - create/configure/run flow,
  - status/progress tracking,
  - output review/comparison,
  - export/download operations,
  - failure handling and retry path.

### B3. Advanced Control Exposure

- UI exposes applicable advanced controls (ControlNet/IPAdapter/consistency
  controls) without requiring raw JSON edits.
- UI validates required fields and constraint ranges before submission.

### B4. Review and Approval Interaction

- UI includes review workflows for baseline-vs-variant comparison and continuity
  checks.
- Review outcomes (approve/reject/comment) are stored and auditable.

### B5. Accessibility and Responsiveness

- Critical user journeys pass:
  - keyboard-only navigation checks,
  - screen-reader labeling checks,
  - contrast checks,
  - responsive viewport checks for supported breakpoints.

## C. Immutable Gate Checks

All checks below must pass to satisfy immutable acceptance.

1. Workflow-class coverage matrix status: all green.
2. UI interaction matrix status: all green.
3. Contract parity checks: pass.
4. E2E certification suite: pass.
5. Cross-functional sign-off matrix: complete.

Any failed item blocks gate completion.

## D. Evidence Requirements

Minimum evidence package:

- Coverage matrix export (workflow classes + UI interactions).
- Contract parity report.
- E2E run report with pass/fail summary.
- Benchmark and consistency report.
- Sign-off record for required functions.

## E. Traceability

Primary checklist item:

- `WS00-005`

Related governance tasks:

- `WS00-003`
- `WS00-004`
- `WS00-007`
