Status: Active
Owner: OSHUN Studio Architecture + OSHUN Security + Program Operations + OSHUN
Web + OSHUN BFF
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0030-oshun-studio-notification-center.mddocs/releases/v1/specs/studio-notification-center-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-notification-center-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioNotificationCenterWorkspace.tsxapps/oshun/web/src/analytics/studioNotificationCenterTelemetry.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio notification-center governance workflows.
This document is the execution artifact for OST-00144.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| Notification-center route | OSHUN Web | Platform Web | route + analytics contracts |
| Notification ingestion + dedupe engine | OSHUN BFF | Data Platform | envelope schema + dedupe pipelines |
| Triage + assignment operations | Program Operations | Domain Integrators | assignment workflow services |
| Critical escalation workflows | OSHUN Security | Incident Response | on-call routing + escalation channels |
| Audit/compliance evidence stream | Data Platform + Compliance | Security | audit event ingestion + retention controls |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| Notification-center flow success rate | >= 99.0% | < 98.0% over 15 min |
| Critical alert escalation timeliness | <= 5 min | > 8 min over 10 min |
| Deduplication correctness | 100% deterministic | any incorrect merge/collision |
| Notification-center flow p95 latency | <= 2200ms | > 3200ms over 15 min |
| Notification audit event completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Feed Triage and Prioritization Failures#
Trigger: repeated NOTIFICATION_FEED_TRIAGE_FAILED outcomes.
Actions:
- Validate severity classification and priority scoring contracts.
- Inspect ordering pipeline and dedupe interaction behavior.
- Re-run triage flow in preview with tracing enabled.
- Block notification-policy promotion until deterministic ordering recovers.
3.2 Acknowledge and Assign Failures#
Trigger: repeated NOTIFICATION_ACK_ASSIGN_FAILED outcomes.
Actions:
- Validate assignment transition schema and assignee identity mapping.
- Inspect ownership workflow service latency and queue health.
- Re-run assignment flow with deterministic actor context.
- Escalate to program operations if assignment backlog exceeds threshold.
3.3 Resolve and Close Failures#
Trigger: repeated NOTIFICATION_RESOLVE_CLOSE_FAILED outcomes.
Actions:
- Validate closure-evidence requirements and policy-state transitions.
- Inspect remediation evidence references for stale/invalid payloads.
- Re-run resolution workflow after evidence integrity checks.
- Freeze resolution promotion if unresolved critical dependencies remain.
3.4 Critical Escalation Failures#
Trigger: repeated NOTIFICATION_CRITICAL_ESCALATION_FAILED outcomes.
Actions:
- Validate escalation channel routing and on-call destination health.
- Inspect policy gates for release-channel and role allowlists.
- Re-run escalation in controlled mode with security reviewer oversight.
- Route fallback escalation to incident command if channel delivery fails.
3.5 Deduplication Integrity Failures#
Trigger: repeated NOTIFICATION_DEDUPLICATION_REVIEW_FAILED outcomes.
Actions:
- Validate dedupe keys and collision-protection contracts.
- Inspect merged-notification context for incident mismatch.
- Re-run dedupe review with collision diagnostics enabled.
- Roll back dedupe rule changes that violate signal integrity.
3.6 Policy Denial Spike#
Trigger: unexpected increase in ROLE_POLICY_DENIED or production-policy
denials.
Actions:
- Compare flow allowlists with active entitlement policy bundles.
- Inspect recent role or policy-release changes for drift.
- Apply policy hotfix or roll back drifted contract version.
- Confirm deny-rate normalization after mitigation.
3.7 Telemetry and Audit Degradation#
Trigger: missing or delayed notification-center telemetry/audit events.
Actions:
- Validate analytics sink health and ingestion queue depth.
- Enable degraded-observability warning in workspace operations.
- Replay buffered notification lifecycle events.
- Confirm event completeness and SLO recovery.
4. Release Checklist#
- Validate
/studio/notification-centerrenders and executes required flows. - Validate optimistic, error, and retry behavior for each flow.
- Validate role-policy allow/deny and production escalation enforcement.
- Validate telemetry/audit emissions and SLO panel updates.
- Validate integration/e2e/accessibility evidence artifacts.
5. Incident Communication Templates#
Incident Start#
[P{severity}] Studio Notification Center Incident
Detected: {timestamp}
Impact: {triage | assignment | resolution | escalation | dedupe impact}
Suspected cause: {policy drift | routing issue | dedupe contract regression}
Owner: {on-call}
Incident Update#
[P{severity}] Studio Notification Center Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {feedTriagePrioritization | acknowledgeAssignWorkflow | resolveCloseLoop | criticalEscalationHandling | deduplicationIntegrityReview}
ETA: {time}
Incident Resolved#
[P{severity}] Studio Notification Center 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 |
| Notification ingestion + dedupe | #oshun-bff |
BFF lead |
| Program operations and assignment governance | #oshun-program-ops |
Program operations lead |
| Critical escalation + policy governance | #oshun-security |
Security lead |
| Telemetry and compliance evidence | #oshun-data-platform |
Data platform/SRE lead |
7. Acceptance Criteria (OST-00144)#
OST-00144 is complete only when:
- Ownership and decision authority are documented.
- Notification-center SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.