Status: Active
Owner: OSHUN Studio Architecture + OSHUN Web + OSHUN BFF
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0023-oshun-studio-workspace-context-switching.mddocs/releases/v1/specs/studio-workspace-context-switching-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-workspace-context-switching-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioWorkspaceContextSwitchingWorkspace.tsxapps/oshun/web/src/analytics/studioWorkspaceContextSwitchingTelemetry.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio workspace context-switching governance workflows.
This document is the execution artifact for OST-00088.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| Workspace context-switching route | OSHUN Web | Platform Web | route + analytics contracts |
| Context envelope and transaction contracts | Studio Architecture + BFF | Domain Integrators | schema + policy contracts |
| Continuity and back-stack preservation | Navigation Platform | Web Platform | route context and fallback mappings |
| Role-policy and entitlement checks | Security + Platform Identity | Ops | identity/session payloads |
| Telemetry and audit pipeline | Data Platform | SRE | event sinks + ingestion pipelines |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| Context-switch flow success rate | >= 99.0% | < 98.0% over 15 min |
| Context commit integrity | 100% deterministic commit/rollback | any false pass |
| Policy decision correctness | 100% policy-consistent | any false allow |
| Context-switch flow p95 latency | <= 2200ms | > 3200ms over 15 min |
| Context-switch audit completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Context Switch Commit Failures#
Trigger: repeated CONTEXT_SWITCH_COMMIT_FAILED outcomes.
Actions:
- Inspect source/target context payload and preflight diagnostics.
- Validate target scope availability and schema compatibility.
- Re-run commit in preview with transaction diagnostics enabled.
- Roll back to last certified context-switch contract if needed.
3.2 Continuity Preservation Failures#
Trigger: repeated CONTINUITY_VALIDATION_FAILED outcomes.
Actions:
- Inspect origin/back-stack continuity payload and route mapping logs.
- Validate pending-flow hint persistence and fallback route mapping.
- Apply continuity-mapping hotfix.
- Re-run validation and block promotion until continuity passes.
3.3 Rollback Recovery Failures#
Trigger: repeated ROLLBACK_RECOVERY_FAILED outcomes.
Actions:
- Inspect rollback checkpoint integrity and stale-context diagnostics.
- Rebuild last confirmed context checkpoint.
- Re-run rollback drill in controlled preview scope.
- Freeze release promotion until rollback recovery is deterministic.
3.4 Policy Denial Spike#
Trigger: unexpected increase in ROLE_POLICY_DENIED outcomes.
Actions:
- Compare flow policy map against entitlement contracts.
- Verify recent identity payload/version changes.
- Apply policy hotfix or rollback entitlement drift.
- Confirm deny-rate normalization after mitigation.
3.5 Telemetry and Audit Degradation#
Trigger: missing or delayed context-switch telemetry/audit events.
Actions:
- Validate analytics sink health and queue depth.
- Enable degraded-observability warning in workspace.
- Reconcile missed events from buffered traces.
- Confirm event completeness and SLO recovery.
4. Release Checklist#
- Validate
/studio/workspace-context-switchingrenders and executes required flows. - Validate optimistic, error, and retry behavior for each flow.
- Validate role-policy allow/deny behavior.
- Validate telemetry/audit emissions and SLO panel updates.
- Validate integration/e2e/accessibility evidence artifacts.
5. Incident Communication Templates#
Incident Start#
text
[P{severity}] Studio Workspace Context Switching Incident
Detected: {timestamp}
Impact: {commit/continuity/rollback impact}
Suspected cause: {contract regression | continuity drift | rollback failure | policy drift}
Owner: {on-call}
Incident Update#
text
[P{severity}] Studio Workspace Context Switching Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {contextSwitchCommit | continuityPreservationValidation | rollbackRecoveryDrill}
ETA: {time}
Incident Resolved#
text
[P{severity}] Studio Workspace Context Switching 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 workspace | #oshun-web |
Platform on-call |
| Context contracts and architecture | #oshun-architecture |
Architecture council |
| Route continuity and navigation | #oshun-navigation |
Navigation architecture lead |
| Policy and permissions | #oshun-security |
Security lead |
| Telemetry pipeline and reliability | #oshun-data-platform |
SRE lead |
7. Acceptance Criteria (OST-00088)#
OST-00088 is complete only when:
- Ownership and decision authority are documented.
- Workspace context-switching SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.