Status: Active
Owner: OSHUN Studio Product Design + OSHUN Web + OSHUN BFF
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0021-oshun-studio-search-and-global-discovery.mddocs/releases/v1/specs/studio-search-and-global-discovery-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-search-and-global-discovery-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioSearchDiscoveryWorkspace.tsxapps/oshun/bff/src/routes/search.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio search and global discovery governance workflows.
This document is the execution artifact for OST-00072.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| Search/discovery workspace route | OSHUN Web | Platform Web | route + analytics contracts |
| Search API and ranking logic | OSHUN BFF | Data Platform | BFF route + ranking modules |
| Discovery UI and action routing | OSHUN Web + Navigation | Product Design | route mapping + context hydration |
| Policy and scope enforcement | Security + Product Ops | Platform Identity | entitlement/session payloads |
| Telemetry and audit pipeline | Data Platform | SRE | sinks and ingestion pipelines |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| Search/discovery flow success rate | >= 99.0% | < 98.0% over 15 min |
| Ranking determinism validation integrity | 100% deterministic | any false pass |
| Cross-domain parity sync success rate | >= 99.5% | < 99.0% over 15 min |
| Search/discovery flow p95 latency | <= 2200ms | > 3200ms over 15 min |
| Search/discovery audit completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Discovery Index Publish Failures#
Trigger: repeated DISCOVERY_INDEX_SCHEMA_FAILED outcomes.
Actions:
- Inspect index schema and query contract diagnostics.
- Validate compatibility with route payload contracts.
- Re-run publish in preview with diagnostics enabled.
- Roll back to last certified discovery bundle if needed.
3.2 Relevance Calibration Failures#
Trigger: repeated RELEVANCE_CALIBRATION_FAILED outcomes.
Actions:
- Compare ranking outputs to deterministic baseline fixtures.
- Validate tie-break behavior and domain-intent weighting.
- Apply ranking calibration adjustments.
- Re-run validation and block promotion until pass.
3.3 Cross-Domain Discovery Drift#
Trigger: DISCOVERY_PARITY_DRIFT findings.
Actions:
- Generate drift report by domain and result-action mapping.
- Re-apply canonical discovery contracts.
- Re-run parity checks.
- Freeze release channel promotion until parity is restored.
3.4 Policy Denial Spike#
Trigger: unexpected increase in ROLE_POLICY_DENIED outcomes.
Actions:
- Compare discovery 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 search/discovery 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/search-discoveryrenders 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 Search/Discovery Incident
Detected: {timestamp}
Impact: {index/calibration/parity impact}
Suspected cause: {schema issue | ranking regression | parity drift | policy drift}
Owner: {on-call}
Incident Update#
text
[P{severity}] Studio Search/Discovery Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {discoveryIndexPublish | relevanceCalibrationValidation | crossDomainSearchParitySync}
ETA: {time}
Incident Resolved#
text
[P{severity}] Studio Search/Discovery 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 |
| Search API/ranking behavior | #oshun-bff |
Search architecture lead |
| Navigation and result routing | #oshun-navigation |
Navigation architecture lead |
| Policy and permissions | #oshun-security |
Security lead |
| Telemetry pipeline | #oshun-data-platform |
SRE lead |
7. Acceptance Criteria (OST-00072)#
OST-00072 is complete only when:
- Ownership and decision authority are documented.
- Search/discovery SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.