iiRecord
Agentic AI Atlas · On-Call Rotation
workflow:on-call-rotationa5c.ai
II.
Workflow JSON

workflow:on-call-rotation

Structured · live

On-Call Rotation json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · domain/workflows/workflows-operational.yamlCluster · domain
Record JSON
{
  "id": "workflow:on-call-rotation",
  "_kind": "Workflow",
  "_file": "domain/workflows/workflows-operational.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "On-Call Rotation",
    "description": "Scheduled weekly operational workflow that ensures 24/7 engineering coverage for\nproduction systems. An on-call schedule is maintained in PagerDuty or equivalent,\nwith primary and secondary responders drawn from the team roster. At the start of\neach rotation the incoming on-call engineer reviews open incidents, recent deploys,\nand any known fragile areas. Alerts are tuned periodically to reduce noise and\nprevent alert fatigue. At rotation handoff, the outgoing engineer documents any\nunresolved issues and shares a brief handoff summary. The workflow distributes\noperational burden equitably and keeps response times within SLA thresholds.\n",
    "workflowKind": "operational",
    "triggerType": "scheduled",
    "typicalCadence": "weekly",
    "complexity": "simple"
  },
  "outgoingEdges": [
    {
      "from": "workflow:on-call-rotation",
      "to": "role:sre",
      "kind": "involves_role"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "role:backend-engineer",
      "kind": "involves_role"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "role:devops-engineer",
      "kind": "involves_role"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "role:engineering-manager",
      "kind": "involves_role"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "domain:observability",
      "kind": "applies_to_domain"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "domain:devops",
      "kind": "applies_to_domain"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "responsibility:on-call",
      "kind": "triggers_responsibility"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "responsibility:sla-management",
      "kind": "triggers_responsibility"
    },
    {
      "from": "workflow:on-call-rotation",
      "to": "responsibility:knowledge-sharing",
      "kind": "triggers_responsibility"
    }
  ],
  "incomingEdges": [
    {
      "from": "stack-profile:erlang-otp-telecom",
      "to": "workflow:on-call-rotation",
      "kind": "follows_workflow"
    },
    {
      "from": "lib-agent:devops-sre-platform--sre-expert",
      "to": "workflow:on-call-rotation",
      "kind": "lib_implements_workflow",
      "attributes": {
        "weight": 0.7
      }
    },
    {
      "from": "lib-process:devops-sre-platform--oncall-setup",
      "to": "workflow:on-call-rotation",
      "kind": "lib_implements_workflow",
      "attributes": {
        "weight": 1
      }
    },
    {
      "from": "lib-process:observability--incident-lifecycle",
      "to": "workflow:on-call-rotation",
      "kind": "lib_implements_workflow",
      "attributes": {
        "weight": 0.7
      }
    }
  ]
}