Eve library

OSHUN Studio Complex Interaction Patterns Runbook

Runbook

Revision 1

On this page

Status: Active
Owner: OSHUN Studio Product Design + OSHUN Web
Last Updated: 2026-02-23
Related:

  • docs/adr/ADR-0019-oshun-studio-complex-interaction-patterns-and-state-orchestration.md
  • docs/releases/v1/specs/studio-complex-interaction-patterns-dependency-and-data-contract-map.md
  • docs/releases/v1/specs/studio-complex-interaction-patterns-user-journeys-and-edge-cases.md
  • apps/oshun/web/src/components/studio/StudioComplexInteractionPatternsWorkspace.tsx

Purpose#

Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio complex-interaction governance workflows.

This document is the execution artifact for OST-00056.

1. Ownership Model#

Surface Primary Owner Backup Owner Dependencies
Complex-interactions workspace route OSHUN Web Platform Web route + analytics contracts
Orchestration bundle governance Product Design + Platform UI Design Systems workflow/state contracts
Transition/recovery validation Accessibility QA + Web Product Quality validation harnesses
Domain interaction parity sync Domain adapters + QA Program ops domain integration contracts
Telemetry and audit pipeline Data Platform SRE event sinks + ingestion pipelines

2. Core SLOs#

Metric Target Alert Threshold
Complex-interaction flow success rate >= 99.0% < 98.0% over 15 min
Transition/recovery validation integrity 100% deterministic any false pass
Domain interaction parity success rate >= 99.5% < 99.0% over 15 min
Complex-interaction flow p95 latency <= 2200ms > 3200ms over 15 min
Complex-interaction audit completeness >= 99.5% < 99.0% over 15 min

3. Operational Playbooks#

3.1 Orchestration Publish Failures#

Trigger: repeated ORCHESTRATION_TRANSITION_CONFLICT outcomes.

Actions:

  1. Inspect transition graph diagnostics and invalid-state edges.
  2. Verify workflow bundle schema and state-contract compatibility.
  3. Re-run publish in preview with debug diagnostics enabled.
  4. Roll back to last certified orchestration bundle if needed.

3.2 Recovery Contract Failures#

Trigger: repeated RECOVERY_CONTRACT_FAILED outcomes.

Actions:

  1. Identify failing retry/reset/rollback branches by workflow.
  2. Validate deterministic outcomes for cancellation/timeouts.
  3. Apply remediation in orchestration definitions.
  4. Re-run validation and block promotion until pass.

3.3 Domain Interaction Drift#

Trigger: DOMAIN_INTERACTION_DRIFT findings.

Actions:

  1. Generate drift report by domain/workflow/surface.
  2. Re-apply canonical orchestration bundle references.
  3. Re-run parity checks and confirm pass.
  4. Freeze release channel promotion until drift is resolved.

3.4 Policy Denial Spike#

Trigger: unexpected increase in ROLE_POLICY_DENIED outcomes.

Actions:

  1. Compare UI flow policy map against entitlement contracts.
  2. Verify identity payload/version changes from upstream services.
  3. Apply policy hotfix or rollback entitlement drift.
  4. Confirm denial rates normalize after remediation.

3.5 Telemetry and Audit Degradation#

Trigger: missing or delayed complex-interaction telemetry/audit events.

Actions:

  1. Validate sink health and queue depth.
  2. Enable degraded-observability warning in workspace.
  3. Reconcile missing events from buffered traces.
  4. Confirm event completeness and SLO recovery.

4. Release Checklist#

  • Validate /studio/complex-interactions renders and executes all 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 Complex Interactions Incident
Detected: {timestamp}
Impact: {publish/validation/parity impact}
Suspected cause: {transition conflict | recovery regression | parity drift | policy drift}
Owner: {on-call}

Incident Update#

text
[P{severity}] Studio Complex Interactions Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {orchestrationBundlePublish | transitionRecoveryValidation | domainInteractionParitySync}
ETA: {time}

Incident Resolved#

text
[P{severity}] Studio Complex Interactions 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
Workflow and interaction orchestration #oshun-product-design Interaction architecture lead
Domain parity and integration #project-obsidian-ops Domain integration lead
Policy and permissions #oshun-security Security lead
Telemetry pipeline #oshun-data-platform SRE lead

7. Acceptance Criteria (OST-00056)#

OST-00056 is complete only when:

  1. Ownership and decision authority are documented.
  2. Complex-interaction SLOs and alert thresholds are documented.
  3. At least five playbooks are documented for major failure modes.
  4. Release checklist, communication templates, and escalation paths exist.