Skip to content
OpenCorvus

Inspect the team before use

Active database publication

Service Reliability Incident Operations

Service-level, observability, alert-quality, incident coordination, handoff, post-incident learning, and action evidence joined into a bounded reliability review pack.

Install in OpenCorvusDownload this exact revisionTrust model

Opens the installed OpenCorvus desktop app. The client re-downloads and re-verifies this exact revision, then asks you for an install scope. No desktop app yet? Install OpenCorvus first

Bound execution graph

Workflow and handoffs

The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.

Bound revision · 1 workflows · 5 nodes · 5 Agents
Bound revision14ed3768
01Service Reliability Incident Review5 nodes
  1. 01reliability-sli-slo-error-budget-analystReconciles service boundaries, SLI/SLO definitions, windows, exclusions, and error-budget evidence.root
  2. 02reliability-observability-alert-quality-analystMaps telemetry, queries, alerts, routing, blind spots, and signal quality.root
  3. 03reliability-incident-coordination-handoff-analystBuilds incident timeline, impact, roles, decision, and handoff evidence without operational command.root
  4. 04reliability-postincident-learning-action-analystBuilds blameless contributing-factor, counterevidence, learning, and action records.root
  5. 05service-reliability-incident-review-ownerJoins all four branches, preserves conflicts and unknowns, and routes every production decision to authorized responders.← reliability-incident-coordination-handoff-analyst + reliability-observability-alert-quality-analyst + reliability-postincident-learning-action-analyst + reliability-sli-slo-error-budget-analyst
Evidence output1

Intended scope

Use for source-grounded service reliability and incident evidence without production mitigation, severity declaration, paging, or external communication.

  • Product pillarswork
  • Agent roster5 declared roles
  • Declared workflows1 complete responsibility and dependency graphs
  • Full capability projection1 Skills · 3 tools · 0 MCP refs

Walkthrough pinned revision

Role and dependency walkthrough

This workflow explanation is pinned to the current package digest. It is not a running Agent session, timer, or generated language-model output. Real execution occurs in the OpenCorvus client.

builtin/service-reliability-incident-operations@2026.08.13.1package sha256:14ed3768d35e8bd3ffd9efd97fdf1e149dd1d164dc1b78ad98d6f52c33b5a201

A node becomes schedulable only after its depends_on evidence is terminal. This page explains that contract and does not advance runtime state.

service-reliability-incident-review

Service Reliability Incident Review

  1. 01reliability-sli-slo-error-budget-analystdepends_on: []
  2. 02reliability-observability-alert-quality-analystdepends_on: []
  3. 03reliability-incident-coordination-handoff-analystdepends_on: []
  4. 04reliability-postincident-learning-action-analystdepends_on: []
  5. 05service-reliability-incident-review-ownerdepends_on: reliability-incident-coordination-handoff-analyst, reliability-observability-alert-quality-analyst, reliability-postincident-learning-action-analyst, reliability-sli-slo-error-budget-analyst

Install handoff boundary

The OpenCorvus client owns the real scope choice when a later import is performed. This page only explains project and global behavior and does not submit an install itself.

The client requires an explicit scope

Project scopeApplies only inside the current project; the same package ID overrides a global installation.
User-global scopeAvailable to the current user, but never silently overrides a project installation.

The public page hands over one exact revision, or completes a signed bundle download. It never batch-installs or activates a team. The scope explanation describes client responsibility; it is not a web form that can be submitted.