{
  "id": "workflow:cloud-cost-anomaly-detection",
  "_kind": "Workflow",
  "_file": "workflows/workflows/workflows-infrastructure.yaml",
  "_cluster": "workflows",
  "attributes": {
    "displayName": "Cloud Cost Anomaly Detection",
    "workflowKind": "operational",
    "triggerType": "continuous",
    "typicalCadence": "daily",
    "complexity": "cross-team",
    "description": "Monitors cloud spend for unexpected spikes and anomalous patterns —\nconfiguring cost alerts, investigating billing anomalies, attributing\nspend to teams, and triggering remediation for runaway resources. Excludes\nlong-term cost optimization strategy.\n"
  },
  "outgoingEdges": [
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "role:cloud-architect",
      "kind": "involves_role",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "role:platform-engineer",
      "kind": "involves_role",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "role:engineering-manager",
      "kind": "involves_role",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "skill-area:observability-pipeline",
      "kind": "requires_skill_area",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "skill-area:sli-slo-management",
      "kind": "requires_skill_area",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "domain:cloud-infra",
      "kind": "applies_to_domain",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "domain:infrastructure",
      "kind": "applies_to_domain",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "responsibility:cost-optimization",
      "kind": "triggers_responsibility",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "responsibility:respond-incidents",
      "kind": "triggers_responsibility",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "org-unit:platform-team",
      "kind": "performed_by_org_unit",
      "attributes": {}
    },
    {
      "from": "workflow:cloud-cost-anomaly-detection",
      "to": "org-unit:infra-engineering",
      "kind": "performed_by_org_unit",
      "attributes": {}
    }
  ],
  "incomingEdges": [
    {
      "from": "tool:linode",
      "to": "workflow:cloud-cost-anomaly-detection",
      "kind": "supports_work",
      "attributes": {
        "confidence": "medium",
        "evidence": "Cloud usage and resource metadata are cost-anomaly inputs."
      }
    },
    {
      "from": "tool-server:mcp-pulumi",
      "to": "workflow:cloud-cost-anomaly-detection",
      "kind": "supports_work",
      "attributes": {
        "confidence": "medium",
        "evidence": "IaC inventory and stack metadata can support cost anomaly analysis."
      }
    }
  ]
}