Status: Active
Owner: OSHUN Studio Architecture + OSHUN Web + OSHUN BFF + OSHUN Security +
Program Operations
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0036-oshun-studio-file-and-media-ingestion.mddocs/releases/v1/specs/studio-file-and-media-ingestion-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-file-and-media-ingestion-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioFileMediaIngestionWorkspace.tsxapps/oshun/web/src/analytics/studioFileMediaIngestionTelemetry.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio file/media ingestion workflows.
This document is the execution artifact for OST-00192.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| File/media ingestion workspace route | OSHUN Web | Platform Web | route contracts + ingestion UX orchestration |
| Ingestion envelope persistence | OSHUN BFF | Platform SRE | ingestion APIs + metadata contracts |
| Validation and classification service | Security + Compliance | Platform SRE | validation engine + policy bundles |
| Processing/transformation lifecycle | Platform SRE + BFF | Data Platform | processing workers + storage/transcode pipelines |
| Governance evidence export | Data Platform + Security | Program Operations | audit streams + retention/export controls |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| File/media ingestion flow success rate | >= 99.0% | < 98.0% over 15 min |
| Validation gate reliability | >= 99.5% | < 99.0% over 15 min |
| Ingestion flow p95 latency | <= 2400ms | > 3400ms over 15 min |
| Processing readiness completion | >= 99.0% | < 98.0% over 15 min |
| Recovery replay/idempotency integrity | >= 99.5% | < 99.0% over 15 min |
| Ingestion audit event completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Ingestion Envelope Submit Failures#
Trigger: repeated INGESTION_SUBMIT_FAILED outcomes.
Actions:
- Validate envelope identity, owner, classification, and checksum metadata.
- Inspect source adapter output for missing fields or malformed values.
- Re-run submit flow in preview with diagnostics enabled.
- Block rollout until envelope validation stability normalizes.
3.2 Validation Gate Failures#
Trigger: repeated INGESTION_VALIDATION_FAILED outcomes.
Actions:
- Validate type, size, checksum, and policy check configuration.
- Inspect validation pipeline traces for deterministic failure code mapping.
- Re-run validation gate with policy diagnostics enabled.
- Pause ingestion promotion until gate reliability recovers.
3.3 Processing Lifecycle Failures#
Trigger: repeated INGESTION_PROCESSING_FAILED outcomes.
Actions:
- Validate worker queue health and transformation pipeline dependencies.
- Inspect lifecycle transition logs for deterministic state progression.
- Re-run processing flow with controlled test payload.
- Escalate to Platform SRE if readiness conversion remains unstable.
3.4 Recovery Failures#
Trigger: repeated INGESTION_RECOVERY_FAILED outcomes.
Actions:
- Validate retry/replay/rollback action contracts and idempotency invariants.
- Inspect recovery action traces for policy and lineage drift.
- Re-run recovery with restricted blast-radius controls.
- Freeze manual recovery actions until integrity checks pass.
3.5 Governance Export Failures#
Trigger: repeated INGESTION_GOVERNANCE_EXPORT_FAILED outcomes.
Actions:
- Validate evidence package completeness and retention tagging.
- Inspect export pipeline for schema and storage contract mismatches.
- Re-run export with compliance reviewer oversight.
- Block production evidence exports until validation passes.
3.6 Policy Denial Spike#
Trigger: unexpected rise in ROLE_POLICY_DENIED,
CONFIDENTIAL_INGESTION_POLICY_DENIED, MANUAL_OVERRIDE_POLICY_DENIED, or
PRODUCTION_GOVERNANCE_EXPORT_POLICY_DENIED.
Actions:
- Compare flow allowlists against active RBAC and policy bundles.
- Inspect recent policy release changes for drift.
- Apply policy hotfix or roll back drifted policy bundle.
- Confirm deny-rate normalization and workflow impact resolution.
3.7 Telemetry and Audit Degradation#
Trigger: missing or delayed ingestion telemetry/audit events.
Actions:
- Validate analytics sink health and ingestion backlog.
- Enable degraded-observability warning in ingestion workspace.
- Replay buffered events where supported.
- Confirm SLO and evidence stream completeness after recovery.
4. Release Checklist#
- Validate
/studio/file-media-ingestionrenders and executes required flows. - Validate optimistic, error, and retry behavior for each flow.
- Validate classification, recovery, and governance policy enforcement.
- Validate telemetry/audit emissions and SLO panel updates.
- Validate integration/e2e/accessibility evidence artifacts.
5. Incident Communication Templates#
Incident Start#
[P{severity}] Studio File/Media Ingestion Incident
Detected: {timestamp}
Impact: {envelope-submit | validation-gate | processing-lifecycle | recovery-action | governance-export}
Suspected cause: {policy drift | pipeline regression | retention export failure}
Owner: {on-call}
Incident Update#
[P{severity}] Studio File/Media Ingestion Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {submitIngestionEnvelope | executeValidationGate | runProcessingLifecycle | recoverFailedIngestion | exportGovernanceEvidence}
ETA: {time}
Incident Resolved#
[P{severity}] Studio File/Media Ingestion 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 |
|---|---|---|
| Web runtime and ingestion workspace | #oshun-web |
Platform on-call |
| Ingestion persistence and lifecycle | #oshun-bff |
BFF lead |
| Validation and policy governance | #oshun-security |
Security lead |
| Processing/recovery infrastructure | #oshun-platform-sre |
SRE lead |
| Audit/compliance evidence pipelines | #oshun-data-platform |
Data platform/SRE lead |
7. Acceptance Criteria (OST-00192)#
OST-00192 is complete only when:
- Ownership and decision authority are documented.
- File/media ingestion SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.