# OSHUN Studio Accessibility Governance Runbook

Status: Active  
Owner: OSHUN Studio Architecture + OSHUN Web + OSHUN BFF + Platform SRE + OSHUN
Data/Analytics + OSHUN Security + Compliance + Program Operations  
Last Updated: 2026-02-23  
Related:

- `docs/adr/ADR-0044-oshun-studio-accessibility-governance.md`
- `docs/releases/v1/specs/studio-accessibility-governance-dependency-and-data-contract-map.md`
- `docs/releases/v1/specs/studio-accessibility-governance-user-journeys-and-edge-cases.md`
- `apps/oshun/web/src/components/studio/StudioAccessibilityGovernanceWorkspace.tsx`
- `apps/oshun/web/src/analytics/studioAccessibilityGovernanceTelemetry.ts`

## Purpose

Define operational ownership, SLOs, incident playbooks, and escalation paths for
Studio accessibility governance workflows.

This document is the execution artifact for `OST-00256`.

## 1. Ownership Model

| Surface                                    | Primary Owner            | Backup Owner       | Dependencies                                       |
| ------------------------------------------ | ------------------------ | ------------------ | -------------------------------------------------- |
| Accessibility governance workspace route   | OSHUN Web                | Platform Web       | route contracts + governance UX orchestration      |
| Accessibility contract lifecycle registry  | Design Systems + Web     | BFF                | contract schemas + owner/expiry governance         |
| Validation suite orchestration             | Platform SRE + Web QA    | Data Platform      | axe/keyboard/screen-reader suites + runtime probes |
| Waiver/block policy and approval controls  | Security + Compliance    | Program Operations | RBAC/tier policies + CAB governance                |
| Remediation execution and closure workflow | Web + Platform SRE       | Domain teams       | fix/rollback controls + post-fix validation reruns |
| Telemetry and governance audit evidence    | Data Platform + Security | Platform SRE       | analytics sinks + retention/export controls        |

## 2. Core SLOs

| Metric                                         | Target    | Alert Threshold      |
| ---------------------------------------------- | --------- | -------------------- |
| Accessibility governance flow success rate     | >= 99.0%  | < 98.0% over 15 min  |
| Accessibility contract integrity               | >= 99.5%  | < 99.0% over 15 min  |
| Validation/triage/remediation flow p95 latency | <= 2500ms | > 3500ms over 15 min |
| Validation evidence continuity                 | >= 99.5%  | < 99.0% over 15 min  |
| Policy-tier/CAB enforcement correctness        | >= 99.5%  | < 99.0% over 15 min  |
| Critical issue closure determinism             | >= 99.5%  | < 99.0% over 15 min  |
| Telemetry/audit event delivery continuity      | >= 99.5%  | < 99.0% over 15 min  |

## 3. Operational Playbooks

### 3.1 Contract Publish Failures

Trigger: repeated `ACCESSIBILITY_CONTRACT_PUBLISH_FAILED` outcomes.

Actions:

1. Validate contract identity, scope, severity, and owner metadata.
2. Inspect contract schema compatibility and version drift.
3. Re-run publish in preview channel with validation diagnostics.
4. Block production waiver/remediation path until contract integrity recovers.

### 3.2 Validation Suite Failures

Trigger: repeated `ACCESSIBILITY_VALIDATION_SUITE_FAILED` outcomes.

Actions:

1. Validate failing axe/keyboard/screen-reader artifact references.
2. Inspect test harness drift and flakiness sources.
3. Re-run suites against known-good baseline snapshots.
4. Maintain release block while critical violations remain unresolved.

### 3.3 Issue Triage Failures

Trigger: repeated `ACCESSIBILITY_ISSUE_TRIAGE_FAILED` outcomes.

Actions:

1. Validate contract-to-issue linkage and severity classification.
2. Inspect ownership assignment and issue-state transition validity.
3. Re-run triage with accessibility reviewer oversight.
4. Escalate to program operations if issue routing is inconsistent.

### 3.4 Waiver/Block Decision Failures

Trigger: repeated `ACCESSIBILITY_WAIVER_BLOCK_DECISION_FAILED` outcomes.

Actions:

1. Validate role/tier/CAB prerequisites and reason codes.
2. Inspect policy bundle drift and deny-path anomalies.
3. Re-run decision with compliance auditor supervision.
4. Freeze production promotion path while decision integrity is degraded.

### 3.5 Remediation Closure Failures

Trigger: repeated `ACCESSIBILITY_REMEDIATION_CLOSURE_FAILED` outcomes.

Actions:

1. Validate remediation action payload and issue-state prerequisites.
2. Verify post-fix validation pass evidence before closure.
3. Re-run remediation closure with incident commander support.
4. Prevent closure until deterministic revalidation is complete.

### 3.6 Policy Denial Spike

Trigger: sustained increase in `ROLE_POLICY_DENIED`,
`PERMISSION_TIER_ROLE_DENIED`, `FLOW_PERMISSION_TIER_INSUFFICIENT`,
`POLICY_JUSTIFICATION_REQUIRED`, `CRITICAL_CONTRACT_RESTRICTED_REQUIRED`,
`PRODUCTION_APPROVAL_REQUIRED`, or
`PRODUCTION_WAIVER_REQUIRES_COMPLIANCE_AUDITOR`.

Actions:

1. Compare active role/tier/CAB policy bundles against intended controls.
2. Inspect recent policy changes for deny-path regressions.
3. Roll back or patch policy bundle and revalidate all decision paths.
4. Confirm denial-rate normalization across governance flows.

### 3.7 Telemetry and Audit Degradation

Trigger: missing or delayed `studio_accessibility_governance_*` telemetry
events.

Actions:

1. Validate analytics sink health and ingestion backlog.
2. Enable degraded-observability notice in governance workspace.
3. Replay buffered events where replay semantics are supported.
4. Confirm SLO panel and audit-evidence continuity after recovery.

## 4. Release Checklist

- [ ] Validate `/studio/accessibility-governance` renders and executes required
      flows.
- [ ] Validate optimistic, error, and retry behavior for all governance flows.
- [ ] Validate permission-tier, critical-contract, and production CAB policy
      enforcement.
- [ ] Validate telemetry/audit emissions and SLO panel updates.
- [ ] Validate integration/e2e/accessibility/performance evidence artifacts.

## 5. Incident Communication Templates

### Incident Start

```
[P{severity}] Studio Accessibility Governance Incident
Detected: {timestamp}
Impact: {contract-publish | validation-suite | issue-triage | waiver-block | remediation-closure}
Suspected cause: {policy drift | schema regression | telemetry degradation | test-harness failure}
Owner: {on-call}
```

### Incident Update

```
[P{severity}] Studio Accessibility Governance Update
Time: {timestamp}
Mitigation: {rollback | hotfix | policy patch | release hold}
Affected flows: {publishAccessibilityContract | runAccessibilityValidationSuite | triageAccessibilityIssue | decideAccessibilityWaiverOrBlock | executeAccessibilityRemediationClosure}
ETA: {time}
```

### Incident Resolved

```
[P{severity}] Studio Accessibility Governance Incident Resolved
Resolved: {timestamp}
Root cause: {description}
Fix: {release/hotfix id}
Validation: {tests + telemetry checks}
Postmortem: {link}
```

## 6. Escalation Paths

| Area                                       | Primary Channel        | Escalate To           |
| ------------------------------------------ | ---------------------- | --------------------- |
| Accessibility governance workspace UX      | `#oshun-web`           | Platform on-call      |
| Accessibility contract and validation APIs | `#oshun-bff`           | BFF lead              |
| Accessibility test/runtime monitoring      | `#oshun-platform-sre`  | SRE lead              |
| Policy-tier/CAB governance controls        | `#oshun-security`      | Security + Compliance |
| Accessibility analytics and reporting      | `#oshun-data-platform` | Data platform lead    |

## 7. Acceptance Criteria (OST-00256)

`OST-00256` is complete only when:

1. Ownership and decision authority are documented.
2. Accessibility-governance SLOs and alert thresholds are documented.
3. At least five playbooks are documented for major failure modes.
4. Release checklist, communication templates, and escalation paths exist.
