Status: Active
Owner: OSHUN Studio Architecture + Program Operations + OSHUN Web + OSHUN BFF +
Platform SRE + Security and Compliance + OSHUN Data/Analytics Engineering
Last Updated: 2026-03-23
Related:
docs/adr/ADR-0052-oshun-studio-launch-readiness-governance.mddocs/releases/v1/specs/studio-launch-readiness-governance-dependency-and-data-contract-map.md
Purpose#
Define primary journeys and deterministic edge-case behavior for Studio launch readiness governance workflows.
This document is the execution artifact for OST-00315.
Personas#
- Launch Readiness Manager
- Platform SRE Incident Commander
- Compliance Auditor
- Security Reviewer
- Domain Release Owner
Journey Principles#
- Production go/no-go decisions must be policy-gated and auditable.
- Critical blockers must fail readiness closed unless governed exceptions exist.
- Launch readiness must account for cross-domain dependency health.
- Metis is a first-class launch lane with its own scorecard and blocker queue whenever educational or tutoring flows are in scope.
- Readiness evidence must remain observable and exportable.
1. Primary Journeys#
J1. Build Launch Readiness Scorecard#
Goal: Aggregate release readiness posture across required governance dimensions.
Entry: Launch readiness governance workspace
Steps:
- Select release candidate and channel.
- Ingest domain readiness signals (quality, security, performance, operations, compliance).
- Normalize statuses and severity into scorecard dimensions.
- Validate evidence freshness and owner assignments.
- Materialize a dedicated Metis overlay when the release touches learner, tutoring, or institutional-delivery flows.
- Persist scorecard snapshot and emit governance audit event.
Success State:
- Release scorecard is complete, traceable, and ready for go/no-go evaluation.
- Metis readiness appears as an explicit lane rather than being buried in generic governance notes when educational launch scope exists.
J2. Triage and Assign Launch Blockers#
Goal: Convert failing readiness signals into actionable blocker records with clear ownership.
Entry: Scorecard contains warning or blocked dimensions
Steps:
- Create blocker with domain, category, and severity.
- Assign owner and due time.
- Attach root-cause context and mitigation plan.
- Move blocker through triage and mitigation states.
- Emit blocker lifecycle telemetry and audit continuity.
Success State:
- Every blocker has deterministic state, owner, and mitigation context.
- Metis-specific blockers remain visible as launch blockers until they are mitigated, exception-approved, or closed with evidence.
J3. Evaluate Policy-Aware Go/No-Go Decision#
Goal: Execute governed go/no-go decision with role/tier approval controls.
Entry: Scorecard and blockers reviewed
Steps:
- Validate actor role and permission tier.
- Evaluate unresolved blockers and dependency health constraints.
- Require CAB ticket or approved exception evidence for production decisions.
- Record decision outcome (
go,no_go,go_with_exception) and reason. - Emit approval audit event with trace lineage.
Success State:
- Decision is policy-compliant, reason-coded, and auditable.
J4. Orchestrate Channel Gate Transition#
Goal: Progress launch gate state across preview/staging/production safely.
Entry: Approved decision and gate preconditions satisfied
Steps:
- Recompute release gate state from scorecard, blockers, and approvals.
- Validate channel-specific constraints and incident posture.
- Transition gate status (
open,holding,approved,blocked) as needed. - Notify dependent domain owners of gate transition outcome.
- Emit release-gate transition telemetry and governance audit event.
Success State:
- Release channel gate state is deterministic and aligned with policy.
J5. Recover Launch Readiness Incident and Resume Governance#
Goal: Resolve governance breakdowns and restore launch-control continuity.
Entry:
Readiness incident opened (e.g., telemetry gap, blocker drift, policy mismatch)
Steps:
- Correlate impacted scorecards, blockers, approvals, and gate states.
- Apply mitigation (signal replay, ownership correction, policy patch, exception revoke).
- Re-run scorecard, blocker evaluation, and decision workflow.
- Verify telemetry/audit continuity restoration.
- Close incident with complete readiness evidence package.
Success State:
- Launch readiness governance is restored with auditable closure evidence.
2. Critical Edge Cases#
E1. Missing Required Readiness Dimension#
- Trigger: scorecard generation omits a required dimension.
- Required behavior: deny scorecard completion with
required_dimension_missing.
E2. Stale Evidence Timestamp#
- Trigger: dimension evidence exceeds freshness SLA.
- Required behavior: mark dimension
blockedand create blocker.
E3. Critical Blocker Without Owner#
- Trigger: blocker is critical and owner is empty.
- Required behavior: reject blocker state transition and require ownership.
E4. Blocker Closure Without Mitigation Evidence#
- Trigger: closure attempted without mitigation summary/evidence reference.
- Required behavior: deny closure and keep blocker active.
E5. Production Go Decision Without CAB Ticket#
- Trigger: production
goorgo_with_exceptiondecision lacks CAB evidence. - Required behavior: hard deny with policy audit event.
E6. Permission Tier Below Approval Requirement#
- Trigger: actor tier is below required decision tier.
- Required behavior: deny decision and preserve gate state.
E7. Role Not Allowed for Go/No-Go Action#
- Trigger: non-authorized role attempts production approval decision.
- Required behavior: deny with role-policy reason code.
E8. Dependency Domain Outage During Approval#
- Trigger: upstream/downstream dependency health degrades to critical.
- Required behavior: force gate status
blockedand open blocker.
E9. Go-With-Exception Missing Waiver Rationale#
- Trigger: exception decision selected but waiver rationale is absent.
- Required behavior: deny decision and require explicit rationale.
E10. Telemetry/Audit Sink Degradation#
- Trigger: readiness transitions complete but audit event delivery fails.
- Required behavior: enter degraded-observability mode and block production promotion.
E11. Metis Release Candidate Without Dedicated Overlay#
- Trigger: release scope includes Metis learner or tutoring flows but no Metis scorecard lane is generated.
- Required behavior: treat the dashboard as incomplete and block launch governance progression.
E12. Metis Go Decision With Any Open Production Blocker#
- Trigger: Metis production lane attempts
gowhile any open blocker still targets production. - Required behavior: deny the decision and force
no_goor governed exception handling.
3. Journey-to-Surface Mapping#
| Journey | Primary Surface | Supporting Surfaces |
|---|---|---|
| J1 Build Readiness Scorecard | Readiness scorecard panel | Domain health ingestion + evidence metadata services |
| J2 Triage and Assign Blockers | Blocker management panel | Owner directory + incident/risk tags |
| J3 Evaluate Go/No-Go Decision | Decision and approvals panel | RBAC/tier policy engine + CAB/waiver governance |
| J4 Orchestrate Channel Gate | Release gate transition panel | Deployment channel state + dependency health monitors |
| J5 Recover Readiness Incident | Governance incident panel | Observability dashboards + runbook orchestration |
| Metis overlay management | Metis scorecard spotlight | learner-quality, evidence, safety, and interop feeds |
4. Instrumentation Requirements#
Required events:
launch_readiness.journey.startedlaunch_readiness.journey.step.completedlaunch_readiness.journey.blockedlaunch_readiness.journey.decision.deniedlaunch_readiness.journey.recoveredlaunch_readiness.journey.completed
Required dimensions:
releaseId,releaseChannel,domainScope,scorecardIddimension,dimensionStatus,evidenceRef,evidenceFreshnessMsblockerId,blockerSeverity,blockerCategory,blockerState,ownerdecisionId,decision,approvalTicket,permissionTier,actorRolegateStateId,gateStatus,criticalBlockerCount,hasApprovalEvidenceselectedLane,scorecardStatus,blockerState,incidentStateactorId,journeyId,stepId,outcome,reasonCode,latencyMs,traceId
5. Acceptance Criteria (OST-00315)#
OST-00315 is complete only when:
- At least five launch-readiness journeys are documented.
- At least ten deterministic edge cases are documented.
- Journey-to-surface mapping is explicit.
- Instrumentation requirements and dimensions are documented.