Status: Active
Owner: OSHUN Studio Architecture + Program Operations + OSHUN Security + OSHUN
Web + OSHUN BFF
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0031-oshun-studio-activity-and-change-feeds.mddocs/releases/v1/specs/studio-activity-and-change-feeds-dependency-and-data-contract-map.mddocs/releases/v1/specs/studio-activity-and-change-feeds-user-journeys-and-edge-cases.mdapps/oshun/web/src/components/studio/StudioActivityChangeFeedsWorkspace.tsxapps/oshun/web/src/analytics/studioActivityChangeFeedsTelemetry.ts
Purpose#
Define operational ownership, SLOs, incident playbooks, and escalation paths for Studio activity/change-feed governance workflows.
This document is the execution artifact for OST-00152.
1. Ownership Model#
| Surface | Primary Owner | Backup Owner | Dependencies |
|---|---|---|---|
| Activity/change-feed route | OSHUN Web | Platform Web | route contracts + telemetry hooks |
| Timeline ingestion and ordering | OSHUN BFF | Data Platform | event envelopes + cursor sequencing |
| Attribution verification operations | OSHUN Security | Program Operations | identity mapping + policy contracts |
| Follow-up routing orchestration | Program Operations | Domain Integrators | ownership routing services + queue pipelines |
| Compliance export packaging and evidence | Compliance + Data Platform | Security | export bundle schema + audit event persistence |
2. Core SLOs#
| Metric | Target | Alert Threshold |
|---|---|---|
| Activity/change flow success rate | >= 99.0% | < 98.0% over 15 min |
| Timeline ordering determinism | 100% deterministic | any non-deterministic ordering |
| Attribution verification completeness | >= 99.5% | < 99.0% over 15 min |
| Activity/change flow p95 latency | <= 2400ms | > 3400ms over 15 min |
| Compliance export package completeness | >= 99.5% | < 99.0% over 30 min |
| Activity/change audit event completeness | >= 99.5% | < 99.0% over 15 min |
3. Operational Playbooks#
3.1 Unified Timeline Triage Failures#
Trigger: repeated ACTIVITY_TIMELINE_TRIAGE_FAILED outcomes.
Actions:
- Validate cross-domain severity and time-ordering contract inputs.
- Inspect cursor sequence integrity and replay-window boundaries.
- Re-run triage flow in preview with trace logging enabled.
- Freeze promotion of ordering policy changes until determinism is restored.
3.2 Actor Attribution Verification Failures#
Trigger: repeated ACTIVITY_ATTRIBUTION_VERIFICATION_FAILED outcomes.
Actions:
- Validate actor identity links and source-domain role mapping.
- Inspect attribution evidence records for stale or missing metadata.
- Re-run verification after identity reconciliation.
- Escalate to security if unresolved attribution drift persists.
3.3 Cursor Replay Reconstruction Failures#
Trigger: repeated ACTIVITY_CURSOR_REPLAY_FAILED outcomes.
Actions:
- Validate cursor chain continuity and replay-window semantics.
- Inspect replay dependency failures in ordering and storage services.
- Re-run cursor reconstruction in controlled mode.
- Roll back cursor contract changes if replay determinism degrades.
3.4 Follow-Up Routing Failures#
Trigger: repeated ACTIVITY_FOLLOW_UP_ROUTING_FAILED outcomes.
Actions:
- Validate owner-routing mappings and workflow target resolution.
- Inspect queue processing latency and assignment backlog.
- Re-run follow-up routing with deterministic owner context.
- Escalate to program operations if routing backlog exceeds threshold.
3.5 Compliance Export Packaging Failures#
Trigger: repeated ACTIVITY_COMPLIANCE_EXPORT_FAILED outcomes.
Actions:
- Validate export package schema and evidence attachment contracts.
- Verify attribution prerequisite state for selected change records.
- Re-run export packaging with compliance reviewer oversight.
- Block production export promotion until package validation stabilizes.
3.6 Policy Denial Spike#
Trigger: unexpected increase in ROLE_POLICY_DENIED,
PRODUCTION_EXPORT_POLICY_DENIED, or ATTRIBUTION_VERIFICATION_REQUIRED.
Actions:
- Compare flow allowlists with active entitlement/policy bundles.
- Inspect recent role and release-policy changes for drift.
- Apply policy hotfix or roll back drifted policy revisions.
- Confirm denial-rate normalization after mitigation.
3.7 Telemetry and Audit Degradation#
Trigger: missing or delayed activity/change telemetry or audit events.
Actions:
- Validate analytics sink health and event ingestion queue depth.
- Enable degraded-observability warning for operators.
- Replay buffered events where supported by pipelines.
- Confirm SLO panel data freshness and event completeness recovery.
4. Release Checklist#
- Validate
/studio/activity-change-feedsrenders and executes required flows. - Validate optimistic, error, and retry behavior for each flow.
- Validate role-policy and attribution prerequisite enforcement.
- Validate telemetry/audit emissions and SLO panel updates.
- Validate integration/e2e/accessibility evidence artifacts.
5. Incident Communication Templates#
Incident Start#
[P{severity}] Studio Activity/Change Feeds Incident
Detected: {timestamp}
Impact: {triage | attribution | replay | routing | export}
Suspected cause: {ordering drift | identity mapping issue | policy regression}
Owner: {on-call}
Incident Update#
[P{severity}] Studio Activity/Change Feeds Update
Time: {timestamp}
Mitigation: {rollback | hotfix | degraded mode}
Affected flows: {unifiedTimelineTriage | actorAttributionVerification | cursorReplayReconstruction | followUpRoutingExecution | complianceExportPackaging}
ETA: {time}
Incident Resolved#
[P{severity}] Studio Activity/Change Feeds 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 |
| Activity ingestion and cursor sequencing | #oshun-bff |
BFF lead |
| Follow-up routing and program operations | #oshun-program-ops |
Program operations lead |
| Attribution and export policy governance | #oshun-security |
Security lead |
| Telemetry and compliance evidence | #oshun-data-platform |
Data platform/SRE lead |
7. Acceptance Criteria (OST-00152)#
OST-00152 is complete only when:
- Ownership and decision authority are documented.
- Activity/change-feed SLOs and alert thresholds are documented.
- At least five playbooks are documented for major failure modes.
- Release checklist, communication templates, and escalation paths exist.