# OSHUN Studio Launch Readiness Governance Runbook

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

- `docs/adr/ADR-0052-oshun-studio-launch-readiness-governance.md`
- `docs/releases/v1/specs/studio-launch-readiness-governance-dependency-and-data-contract-map.md`
- `docs/releases/v1/specs/studio-launch-readiness-governance-user-journeys-and-edge-cases.md`
- `apps/oshun/web/src/components/studio/StudioLaunchReadinessGovernanceDashboard.tsx`
- `apps/oshun/web/src/analytics/studioLaunchReadinessGovernanceTelemetry.ts`

## Purpose

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

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

## 1. Ownership Model

| Surface                                 | Primary Owner                     | Backup Owner        | Dependencies                                                |
| --------------------------------------- | --------------------------------- | ------------------- | ----------------------------------------------------------- |
| Launch readiness governance route       | OSHUN Web                         | Platform Web        | workflow UX orchestration + release command navigation      |
| Readiness scorecard aggregation         | Program Operations + Data         | Studio Architecture | domain readiness signal contracts + evidence freshness      |
| Blocker lifecycle and owner assignment  | Program Operations + Domain Leads | Platform SRE        | blocker-state machine + identity directory + escalation     |
| Go/no-go and exception approval control | Security + Compliance             | Program Operations  | role/tier policy enforcement + CAB controls + waiver policy |
| Release channel gate transitions        | Platform SRE + BFF                | Web platform        | channel-state orchestration + dependency-health telemetry   |
| Telemetry and governance audit delivery | Data Platform + Security          | Platform SRE        | analytics sinks + retention/export + replay controls        |
| Metis launch overlay and blocker queue  | Metis Ops + Program Operations    | Security + Platform | tutor evidence posture + operator readiness + release holds |

## 2. Core SLOs

| Metric                                           | Target    | Alert Threshold      |
| ------------------------------------------------ | --------- | -------------------- |
| Launch readiness flow success rate               | >= 99.0%  | < 98.0% over 15 min  |
| Scorecard completeness and freshness integrity   | >= 99.5%  | < 99.0% over 15 min  |
| Blocker triage/decision/gate flow p95            | <= 2500ms | > 3500ms over 15 min |
| Role-tier/CAB/waiver enforcement correctness     | >= 99.5%  | < 99.0% over 15 min  |
| Gate-state recomputation and transition fidelity | >= 99.5%  | < 99.0% over 15 min  |
| Incident 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 Scorecard Aggregation Failures

Trigger: repeated `LAUNCH_READINESS_SCORECARD_FAILED` outcomes.

Actions:

1. Validate release metadata (`releaseId`, `releaseChannel`, domain scope).
2. Inspect dimension completeness, owner assignment, and evidence freshness.
3. Confirm the Metis overlay dimensions (learner quality, grounding, safety,
   interoperability) are present when the release candidate crosses the
   educational substrate.
4. Re-run scorecard generation with diagnostics and source-signal validation.
5. Block go/no-go decisions until scorecard integrity recovers.

### 3.2 Blocker Triage and Assignment Failures

Trigger: repeated `LAUNCH_READINESS_BLOCKER_TRIAGE_FAILED` outcomes.

Actions:

1. Validate blocker severity, category, owner, and due-time metadata.
2. Inspect blocker-state transition drift and orphaned owner assignments.
3. Re-run blocker triage with explicit ownership and mitigation evidence.
4. Escalate unresolved Metis grounding, rights, or admin-readiness blockers to
   the launch commander and Metis ops lead within SLA.
5. Escalate unresolved critical blockers to release command within SLA.

### 3.3 Go/No-Go Decision Governance Denials

Trigger: repeated `LAUNCH_READINESS_DECISION_POLICY_DENIED` outcomes.

Actions:

1. Validate role, permission tier, CAB ticket, and waiver rationale inputs.
2. Inspect policy-bundle version drift and approver-assignment correctness.
3. Re-run decision path with compliance-auditor oversight.
4. Freeze production promotion while policy-governance integrity is degraded.

### 3.4 Release Gate Transition Failures

Trigger: repeated `LAUNCH_READINESS_GATE_TRANSITION_FAILED` outcomes.

Actions:

1. Validate gate-state prerequisites (scorecard readiness + blocker posture +
   approval evidence).
2. Inspect dependency-health signals and incident posture conflicts.
3. Recompute gate state and replay transition under controlled conditions.
4. Hold channel progression until deterministic gate evaluation is restored.

### 3.5 Launch Readiness Incident Recovery Failures

Trigger: repeated `LAUNCH_READINESS_INCIDENT_RECOVERY_FAILED` outcomes.

Actions:

1. Correlate affected scorecards, blockers, decisions, and gate transitions.
2. Apply mitigation (policy patch, blocker ownership repair, signal replay).
3. Re-run end-to-end readiness workflow and verify closure criteria.
4. Keep launch gate blocked until revalidation and evidence export succeed.

### 3.6 Telemetry and Audit Degradation

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

Actions:

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

## 4. Release Checklist

- [ ] Validate `/studio/launch-readiness-governance` renders and executes
      required flows.
- [ ] Validate optimistic, error, and retry behavior across all launch readiness
      flows.
- [ ] Validate permission-tier, waiver, and production CAB policy enforcement.
- [ ] Validate the Metis launch overlay exposes scorecard dimensions and blocker
      counts consistent with the release candidate.
- [ ] Validate telemetry/audit emissions and SLO panel updates.
- [ ] Validate integration/e2e/accessibility/performance evidence artifacts.

## 5. Incident Communication Templates

### Incident Start

```text
[P{severity}] Studio Launch Readiness Incident
Detected: {timestamp}
Impact: {scorecard | blocker-triage | go-no-go-decision | gate-transition | incident-recovery}
Suspected cause: {signal drift | policy enforcement regression | dependency outage | ownership gap | telemetry degradation}
Owner: {on-call}
```

### Incident Update

```text
[P{severity}] Studio Launch Readiness Update
Time: {timestamp}
Mitigation: {policy patch | blocker ownership correction | gate hold | exception revoke | release hold}
Affected flows: {defineLaunchReadinessBaseline | triageLaunchReadinessBlockers | decideLaunchGoNoGo | transitionReleaseChannelGate | recoverLaunchReadinessIncident}
ETA: {time}
```

### Incident Resolved

```text
[P{severity}] Studio Launch Readiness 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           |
| --------------------------------------- | ---------------------- | --------------------- |
| Launch-readiness workspace UX           | `#oshun-web`           | Platform on-call      |
| Scorecard/blocker orchestration APIs    | `#oshun-bff`           | BFF lead              |
| Release gate transitions and dependency | `#oshun-platform-sre`  | SRE lead              |
| Policy-tier/CAB/waiver governance       | `#oshun-security`      | Security + Compliance |
| Telemetry and audit reporting           | `#oshun-data-platform` | Data platform lead    |

## 7. Acceptance Criteria (OST-00320)

`OST-00320` is complete only when:

1. Ownership and decision authority are documented.
2. Launch-readiness 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.
