Eve library

OSHUN Studio Backup and Disaster Recovery UX Dependency and Data Contract Map

Spec

Revision 1

On this page

Status: Active
Owner: OSHUN Studio Architecture + OSHUN Data Platform + OSHUN Web + OSHUN BFF + Platform SRE + Security and Compliance
Last Updated: 2026-02-23
Related: docs/adr/ADR-0051-oshun-studio-backup-and-disaster-recovery-ux.md

Purpose#

Define dependencies and canonical contracts for Studio backup and disaster recovery UX across Yemaya, Isis, Hathor, Aja, Bellona, and Project Obsidian.

This document is the execution artifact for OST-00306.

Sources Used#

  • docs/adr/ADR-0051-oshun-studio-backup-and-disaster-recovery-ux.md
  • docs/adr/ADR-0039-oshun-studio-resilience-and-error-ux.md
  • docs/adr/ADR-0041-oshun-studio-observability-and-operational-dashboards.md
  • docs/releases/v1/runbooks/studio-resilience-and-error-ux-runbook.md
  • docs/releases/v1/runbooks/studio-observability-and-operational-dashboards-runbook.md
  • docs/releases/v1/runbooks/studio-multi-project-operations-runbook.md
  • docs/releases/v1/runbooks/on-call-runbook.md
  • docs/domains/yemaya/features.md
  • docs/domains/isis/features.md
  • docs/domains/hathor/features.md
  • docs/domains/aja/features.md
  • docs/domains/bellona/features.md

1. Dependency Overview#

1.1 Control Surfaces#

  • Backup/DR UX surfaces: Studio backup plan, restore simulation, failover, and recovery verification workspaces.
  • Backup inventory authority: data platform snapshot catalogs and storage tier APIs.
  • Restore/failover orchestration: BFF workflow APIs plus platform orchestrators.
  • Policy/compliance governance: security/compliance approval controls for high-risk recovery actions.
  • Telemetry/audit continuity: analytics and evidence export pipelines.

1.2 Domain Dependency Graph#

  • Backup/DR UX -> Yemaya: content and asset state recovery with dependency integrity checks.
  • Backup/DR UX -> Isis: generation pipeline/job checkpoint restoration and reconciliation.
  • Backup/DR UX -> Hathor: narrative world and publication artifact recovery lineage.
  • Backup/DR UX -> Aja: timeline/media session recovery and event continuity.
  • Backup/DR UX -> Bellona: runtime/release environment failover and rollback checkpoints.
  • Project Obsidian -> all: unified recovery policy baselines and incident command governance.

2. Ownership and Contract Matrix#

Area Owner Consumers Artifact Contract
Backup plan definition and schedule Data Platform + Program Ops Web + BFF + SRE Backup plan payload StudioBackupPlanDefinition
Snapshot inventory and restore points Data Platform + SRE Recovery operators + incident command Restore point payload StudioRestorePointRecord
Restore simulation and impact analysis BFF + Platform SRE Operators + compliance reviewers Simulation payload StudioRestoreSimulationResult
Failover/restore execution Platform SRE + Security Incident commanders + domain owners Execution payload StudioDisasterRecoveryExecution
Recovery verification and closure evidence Security + Compliance + Data Platform Program governance Verification payload StudioRecoveryVerificationReport

3. Canonical Contracts#

3.1 StudioBackupPlanDefinition#

ts
export interface StudioBackupPlanDefinition {
  planId: string;
  planVersion: string;
  sourceDomain: 'yemaya' | 'isis' | 'hathor' | 'aja' | 'bellona' | 'oshun';
  scope: 'dataset' | 'service' | 'environment' | 'cross_domain';
  schedule: string;
  retentionDays: number;
  encryptionProfile: 'default' | 'hardened';
  ownerTeam: string;
}

3.2 StudioRestorePointRecord#

ts
export interface StudioRestorePointRecord {
  restorePointId: string;
  planId: string;
  sourceDomain: 'yemaya' | 'isis' | 'hathor' | 'aja' | 'bellona' | 'oshun';
  createdAt: string;
  coveragePercent: number;
  integrityState: 'verified' | 'warning' | 'failed';
  storageTier: 'hot' | 'warm' | 'cold';
}

3.3 StudioRestoreSimulationResult#

ts
export interface StudioRestoreSimulationResult {
  simulationId: string;
  restorePointId: string;
  mode: 'dry_run';
  estimatedDurationMinutes: number;
  impactedServices: string[];
  integrityRiskScore: number;
  status: 'pending' | 'success' | 'failed';
  completedAt?: string;
}

3.4 StudioDisasterRecoveryExecution#

ts
export interface StudioDisasterRecoveryExecution {
  executionId: string;
  restorePointId: string;
  action: 'restore' | 'failover' | 'rollback';
  releaseChannel: 'preview' | 'staging' | 'production';
  approvalTicket?: string;
  status: 'pending' | 'running' | 'success' | 'failed';
  checkpointId: string;
  startedAt: string;
  completedAt?: string;
}

3.5 StudioRecoveryVerificationReport#

ts
export interface StudioRecoveryVerificationReport {
  reportId: string;
  executionId: string;
  domainChecks: Array<{
    domain: 'yemaya' | 'isis' | 'hathor' | 'aja' | 'bellona' | 'oshun';
    status: 'passed' | 'failed';
    reasonCode?: string;
  }>;
  unresolvedIssueCount: number;
  verifiedBy: string;
  verifiedAt: string;
}

4. Validation Rules#

  • Backup plan updates must reject invalid retention windows and malformed schedules.
  • Restore simulations must fail closed when restore-point integrity is not verified.
  • Production restore/failover execution requires policy-tier and approval evidence.
  • Recovery verification closure must be denied with unresolved domain checks.
  • Telemetry/audit payloads must include actor, trace, action, outcome, and checkpoint identifiers.

5. Acceptance Criteria (OST-00306)#

OST-00306 is complete only when:

  1. This dependency and contract map exists.
  2. Dependencies for all five Studio domains plus Project Obsidian are mapped.
  3. Contracts for backup plans, restore points, restore simulation, execution, and verification reports are documented.
  4. Ownership boundaries and validation rules are explicit.