Status: Active
Owner: OSHUN Studio Architecture + Platform Identity + OSHUN Web + OSHUN BFF
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0026-oshun-studio-session-and-device-management.mddocs/releases/v1/specs/studio-session-and-device-management-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-session-and-device-management-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioSessionDeviceManagementWorkspace.tsxapps/oshun/web/src/analytics/studioSessionDeviceManagementTelemetry.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio session and device management governance workflows.
This document is the execution artifact for OST-00112.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| Session/device management route | OSHUN Web | Platform Web | route + analytics contracts |
| Session inventory contracts | Platform Identity | BFF | session schema + identity services |
| Trusted-device challenge orchestration | Security + Platform Identity | Security Engineering | challenge providers + risk policy |
| Revocation execution and propagation | OSHUN BFF + Platform Identity | Domain Integrators | revoke APIs + domain adapters |
| Telemetry and audit evidence | Data Platform | SRE | event sinks + ingestion pipelines |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| Session/device flow success rate | >= 99.0% | < 98.0% over 15 min |
| Session inventory integrity | 100% deterministic | any malformed inventory accepted |
| Revocation propagation completeness | >= 99.5% | < 99.0% over 15 min |
| Session/device flow p95 latency | <= 2200ms | > 3200ms over 15 min |
| Session/device audit completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Session Inventory Sync Failures#
Trigger: repeated SESSION_INVENTORY_SYNC_FAILED outcomes.
Actions:
- Validate identity/session service health and payload schema freshness.
- Inspect inventory records for missing/duplicate session metadata.
- Re-run sync in preview with schema diagnostics enabled.
- Block privileged controls until inventory consistency is restored.
3.2 Trusted Device Enrollment Failures#
Trigger: repeated TRUSTED_DEVICE_ENROLLMENT_FAILED outcomes.
Actions:
- Validate challenge provider health and attestation contract versions.
- Verify selected device eligibility and trust state.
- Re-run challenge in controlled mode with trace correlation.
- Keep device untrusted until deterministic enrollment succeeds.
3.3 Session Revocation Execution Failures#
Trigger: repeated SESSION_REVOCATION_EXECUTION_FAILED outcomes.
Actions:
- Validate revoke request scope and target resolution.
- Inspect propagation status across enabled Studio domains.
- Retry failed adapters and reconcile partial revocation outcomes.
- Escalate unresolved targets with manual containment guidance.
3.4 Policy Denial Spike#
Trigger: unexpected increase in ROLE_POLICY_DENIED outcomes.
Actions:
- Compare flow policy map against active role entitlements.
- Validate identity claims and role payload version alignment.
- Apply policy hotfix or rollback entitlement drift.
- Confirm deny-rate normalization after mitigation.
3.5 Telemetry and Audit Degradation#
Trigger: missing or delayed session/device telemetry 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/session-device-managementrenders 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 Session and Device Management Incident
Detected: {timestamp}
Impact: {inventory | trust enrollment | revocation impact}
Suspected cause: {identity service issue | challenge provider issue | propagation drift}
Owner: {on-call}
Incident Update#
text
[P{severity}] Studio Session and Device Management Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {sessionInventorySync | trustedDeviceEnrollment | sessionRevocationExecution}
ETA: {time}
Incident Resolved#
text
[P{severity}] Studio Session and Device Management 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 |
| Identity/session contracts | #oshun-identity |
Identity architecture lead |
| Challenge and trust policy | #oshun-security |
Security engineering lead |
| Revocation propagation runtime | #oshun-bff |
BFF architecture lead |
| Telemetry pipeline and reliability | #oshun-data-platform |
SRE lead |
7. Acceptance Criteria (OST-00112)#
OST-00112 is complete only when:
- Ownership and decision authority are documented.
- Session/device management SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.