{
  "id": "methodology:Google-SRE-methodology",
  "_kind": "Methodology",
  "_file": "domain/methodologies/methodologies-expanded.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "Google SRE Methodology",
    "description": "Site Reliability Engineering as practiced at Google — treating operations as\na software engineering problem. Defines service reliability through SLIs, SLOs,\nand error budgets. When error budget is exhausted, feature velocity slows to\nfocus on reliability. Includes practices like toil budgeting (< 50% ops work),\nblameless postmortems, progressive rollouts, and on-call engineering rotations.\n",
    "methodologyKind": "operations",
    "origin": "Google (Ben Treynor Sloss)",
    "yearIntroduced": "2003"
  },
  "outgoingEdges": [
    {
      "from": "methodology:Google-SRE-methodology",
      "to": "domain:site-reliability",
      "kind": "applies_to"
    },
    {
      "from": "methodology:Google-SRE-methodology",
      "to": "domain:devops",
      "kind": "applies_to"
    },
    {
      "from": "methodology:Google-SRE-methodology",
      "to": "platform:krate",
      "kind": "applies_to",
      "attributes": {
        "notes": "Krate implements SRE principles: error budgets, SLIs on platform resources"
      }
    }
  ],
  "incomingEdges": []
}