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.md
Purpose#
Define dependencies and canonical contracts for Studio launch readiness governance across Yemaya, Isis, Hathor, Aja, Bellona, Metis, and Project Obsidian.
This document is the execution artifact for OST-00314.
Sources Used#
docs/adr/ADR-0052-oshun-studio-launch-readiness-governance.mddocs/releases/v1/runbooks/launch-runbook.mddocs/releases/v1/runbooks/on-call-runbook.mddocs/releases/v1/runbooks/studio-review-and-approval-workflows-runbook.mddocs/releases/v1/runbooks/studio-observability-and-operational-dashboards-runbook.mddocs/releases/v1/runbooks/studio-security-hardening-program-runbook.mddocs/releases/v1/runbooks/studio-backup-and-disaster-recovery-ux-runbook.mddocs/domains/yemaya/features.mddocs/domains/isis/features.mddocs/domains/hathor/features.mddocs/domains/aja/features.mddocs/domains/bellona/features.md
1. Dependency Overview#
1.1 Control Surfaces#
- Readiness scorecard UX surface: launch dimensions for quality, security, performance, operations, and compliance.
- Blocker lifecycle governance: triage, owner assignment, mitigation, and closure flows.
- Approval and exception governance: role/tier/CAB/waiver controls for go/no-go decisions.
- Release channel orchestration: preview/staging/production readiness gates and promotion state.
- Telemetry and evidence continuity: launch audit event stream, SLO rollups, and export pathways.
1.2 Domain Dependency Graph#
Launch Readiness -> Yemaya: content/tooling release signal integrity and launch blockers.Launch Readiness -> Isis: generation runtime readiness and policy gating.Launch Readiness -> Hathor: publishing workflow readiness and review completion.Launch Readiness -> Aja: media pipeline readiness and performance gate status.Launch Readiness -> Bellona: runtime/release infrastructure readiness and incident constraints.Launch Readiness -> Metis: learner-quality, grounding, operator-readiness, safety, and interoperability posture for educational launch scope.Project Obsidian -> all: integrated launch command posture and cross-domain go/no-go governance.
2. Ownership and Contract Matrix#
| Area | Owner | Consumers | Artifact | Contract |
|---|---|---|---|---|
| Launch scorecard aggregation | Program Operations + Data/Analytics | Studio leads + release managers | Scorecard payload | StudioLaunchReadinessScorecard |
| Metis overlay readiness signals | Metis Ops + Sophia + Safety | Launch command + compliance | Metis lane payload | StudioLaunchReadinessScorecard |
| Blocker triage and lifecycle state | Domain Leads + Program Ops | Release command + engineering owners | Blocker records | StudioLaunchBlockerRecord |
| Go/no-go and exception approvals | Security + Compliance + Program Ops | Release managers + platform on-call | Approval decision payload | StudioLaunchApprovalDecision |
| Release channel gate state orchestration | Platform SRE + BFF | Deployment workflows + Studio workspaces | Channel gate state payload | StudioLaunchReleaseGateState |
| Audit and governance evidence continuity | Data Platform + Security + Compliance | Compliance reviews + post-incident teams | Governance audit-event feed | StudioLaunchGovernanceAuditEvent |
3. Canonical Contracts#
3.1 StudioLaunchReadinessScorecard#
ts
export interface StudioLaunchReadinessScorecard {
scorecardId: string;
lane: 'customer' | 'admin' | 'platform' | 'governance' | 'metis';
releaseId: string;
releaseChannel: 'preview' | 'staging' | 'production';
domainScope: Array<
'yemaya' | 'isis' | 'hathor' | 'aja' | 'bellona' | 'metis' | 'oshun'
>;
dimensions: Array<{
dimension:
| 'quality'
| 'security'
| 'performance'
| 'operations'
| 'compliance'
| 'learner_quality'
| 'operator_readiness'
| 'grounding_evidence'
| 'safety_and_rights'
| 'interoperability';
status: 'ready' | 'warning' | 'blocked';
owner: string;
evidenceRef: string;
updatedAt: string;
}>;
readinessScore: number;
generatedAt: string;
}
3.2 StudioLaunchBlockerRecord#
ts
export interface StudioLaunchBlockerRecord {
blockerId: string;
releaseId: string;
lane: 'customer' | 'admin' | 'platform' | 'governance' | 'metis';
domain: 'yemaya' | 'isis' | 'hathor' | 'aja' | 'bellona' | 'metis' | 'oshun';
severity: 'warning' | 'high' | 'critical';
category:
| 'quality_regression'
| 'security_gap'
| 'performance_budget_exceeded'
| 'operational_risk'
| 'compliance_gap'
| 'dependency_outage'
| 'grounding_evidence'
| 'admin_readiness'
| 'institutional_interop'
| 'safety_rights';
state: 'open' | 'triage' | 'mitigated' | 'approved_exception' | 'closed';
owner: string;
dueAt?: string;
reasonCode: string;
createdAt: string;
updatedAt: string;
}
3.3 StudioLaunchApprovalDecision#
ts
export interface StudioLaunchApprovalDecision {
decisionId: string;
lane: 'customer' | 'admin' | 'platform' | 'governance' | 'metis';
releaseId: string;
releaseChannel: 'preview' | 'staging' | 'production';
decision: 'go' | 'no_go' | 'go_with_exception';
actorId: string;
actorRole:
| 'release_manager'
| 'platform_sre'
| 'compliance_auditor'
| 'security_reviewer';
permissionTier: 'baseline' | 'sensitive' | 'restricted';
approvalTicket?: string;
waiverReason?: string;
outcome: 'allowed' | 'denied' | 'error';
reasonCode?: string;
decidedAt: string;
}
3.4 StudioLaunchReleaseGateState#
ts
export interface StudioLaunchReleaseGateState {
gateStateId: string;
lane: 'customer' | 'admin' | 'platform' | 'governance' | 'metis';
releaseId: string;
channel: 'preview' | 'staging' | 'production';
gateStatus: 'open' | 'blocked' | 'holding' | 'approved';
blockerCount: number;
criticalBlockerCount: number;
hasApprovalEvidence: boolean;
nextActionOwner: string;
evaluatedAt: string;
}
3.5 StudioLaunchGovernanceAuditEvent#
ts
export interface StudioLaunchGovernanceAuditEvent {
eventId: string;
action:
| 'launch.scorecard.generated'
| 'launch.blocker.created'
| 'launch.blocker.state_changed'
| 'launch.approval.decision'
| 'launch.release_gate.updated';
outcome: 'allowed' | 'denied' | 'success' | 'error';
releaseId: string;
releaseChannel?: 'preview' | 'staging' | 'production';
actorId?: string;
blockerId?: string;
reasonCode?: string;
requestId?: string;
traceId?: string;
occurredAt: string;
}
4. Validation Rules#
- Launch scorecards must include all required readiness dimensions before go/no-go can be evaluated.
- When Metis learner, tutoring, or institutional-delivery flows are part of the release scope, a dedicated Metis lane is required in the scorecard and blocker model.
- Critical unresolved blockers must force gate status to
blockedunless approved exception policy is satisfied. - Production approvals must enforce role/tier policy and valid approval evidence (CAB ticket or governance exception with rationale).
- Release gate states must be recomputed when blocker or approval state changes.
- Governance audit payloads must include actor, action, outcome, and release context for replay/export.
5. Acceptance Criteria (OST-00314)#
OST-00314 is complete only when:
- This dependency and contract map exists.
- Dependencies for all five Studio domains plus Project Obsidian are mapped.
- Contracts for scorecards, blockers, approvals, gate states, and governance audit events are documented.
- Ownership boundaries and validation rules are explicit.