Status: Active
Owner: OSHUN Studio Architecture + OSHUN Web + OSHUN BFF + OSHUN Security +
Program Operations
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0033-oshun-studio-presence-and-cursor-systems.mddocs/releases/v1/specs/studio-presence-and-cursor-systems-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-presence-and-cursor-systems-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioPresenceCursorSystemsWorkspace.tsxapps/oshun/web/src/analytics/studioPresenceCursorSystemsTelemetry.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio presence and cursor system workflows.
This document is the execution artifact for OST-00168.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| Presence/cursor workspace route | OSHUN Web | Platform Web | route contracts + UI orchestration |
| Heartbeat and liveness services | OSHUN BFF | Platform SRE | session heartbeat and timeout pipelines |
| Cursor sequencing and progression | BFF + Data Platform | Studio Architecture | deterministic sequencing and replay semantics |
| Replay and resume recovery pipeline | Reliability + BFF | Platform SRE | replay cursor services + continuity checks |
| Presence/cursor governance evidence | Security + Compliance | Data Platform | telemetry ingestion + retention controls |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| Presence/cursor flow success rate | >= 99.0% | < 98.0% over 15 min |
| Presence join registration reliability | >= 99.5% | < 99.0% over 15 min |
| Presence/cursor flow p95 latency | <= 2200ms | > 3200ms over 15 min |
| Liveness transition accuracy | >= 99.5% | < 99.0% over 15 min |
| Cursor progression determinism | 100% deterministic | any non-deterministic progression |
| Presence/cursor audit event completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Presence Session Join Failures#
Trigger: repeated PRESENCE_SESSION_JOIN_FAILED outcomes.
Actions:
- Validate actor/workspace/session context integrity.
- Inspect join registration pipeline and policy validation output.
- Re-run join flow in preview with diagnostics enabled.
- Block production promotion until registration reliability normalizes.
3.2 Liveness Transition Failures#
Trigger: repeated PRESENCE_LIVENESS_TRANSITION_FAILED outcomes.
Actions:
- Validate heartbeat cadence and timeout threshold configuration.
- Inspect active-idle-offline transition logs for drift.
- Re-run transition flow with controlled heartbeat profile.
- Escalate to reliability on sustained transition inaccuracy.
3.3 Cursor Progression Failures#
Trigger: repeated CURSOR_PROGRESSION_FAILED outcomes.
Actions:
- Validate cursor monotonicity and sequence continuity contracts.
- Inspect progression pipeline for skipped or regressed sequence entries.
- Re-run progression with deterministic replay safeguards.
- Freeze cursor-related rollout when determinism guarantees fail.
3.4 Replay and Resume Recovery Failures#
Trigger: repeated PRESENCE_REPLAY_RESUME_FAILED outcomes.
Actions:
- Validate replay cursor eligibility and retention window integrity.
- Inspect replay pipeline for ordering or gap detection failures.
- Re-run recovery with full snapshot fallback path.
- Trigger incident if reconnect divergence persists.
3.5 Governance Visibility Review Failures#
Trigger: repeated PRESENCE_GOVERNANCE_REVIEW_FAILED outcomes.
Actions:
- Validate visibility scope and policy redaction contracts.
- Inspect governance package completeness and retention tags.
- Re-run visibility review with security reviewer oversight.
- Block production visibility policy rollout until checks pass.
3.6 Policy Denial Spike#
Trigger: unexpected rise in ROLE_POLICY_DENIED,
HIGH_LATENCY_LIVENESS_POLICY_DENIED, or PRODUCTION_VISIBILITY_POLICY_DENIED.
Actions:
- Compare flow allowlists with active RBAC/policy bundles.
- Inspect entitlement release changes for drift.
- Apply policy hotfix or roll back drifted policy bundle.
- Confirm deny-rate normalization and operator impact resolution.
3.7 Telemetry and Audit Degradation#
Trigger: missing or delayed presence/cursor telemetry/audit events.
Actions:
- Validate sink health and ingestion backlog depth.
- Enable degraded-observability warning in workspace.
- Replay buffered events where supported.
- Confirm SLO and evidence stream completeness after recovery.
4. Release Checklist#
- Validate
/studio/presence-cursor-systemsrenders and executes required flows. - Validate optimistic, error, and retry behavior for each flow.
- Validate role-policy and high-latency governance enforcement.
- Validate telemetry/audit emissions and SLO panel updates.
- Validate integration/e2e/accessibility evidence artifacts.
5. Incident Communication Templates#
Incident Start#
[P{severity}] Studio Presence/Cursor Systems Incident
Detected: {timestamp}
Impact: {session-join | liveness-transition | cursor-progression | replay-recovery | governance-visibility}
Suspected cause: {policy drift | sequencing failure | replay continuity regression}
Owner: {on-call}
Incident Update#
[P{severity}] Studio Presence/Cursor Systems Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {presenceSessionJoin | livenessTransitionOrchestration | cursorProgressionExecution | replayResumeRecovery | governanceVisibilityReview}
ETA: {time}
Incident Resolved#
[P{severity}] Studio Presence/Cursor Systems 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 presence workspace | #oshun-web |
Platform on-call |
| Presence heartbeat and session services | #oshun-bff |
BFF lead |
| Cursor sequencing and replay reliability | #oshun-platform-sre |
SRE lead |
| Policy visibility and security controls | #oshun-security |
Security lead |
| Audit/compliance evidence pipelines | #oshun-data-platform |
Data platform/SRE lead |
7. Acceptance Criteria (OST-00168)#
OST-00168 is complete only when:
- Ownership and decision authority are documented.
- Presence/cursor SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.