Publish DevOpsBench-100 v3.2.5 structural-diversity release (part 9)

tasks/dob100-001-rca-analytics-egress-blocked.json

@@ -1546,7 +1546,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_rca_analytics_egress_blocked",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2467,5 +2467,5 @@
   },
   "task_id": "dob100-001-rca-analytics-egress-blocked",
   "task_name": "Analytics connections are refused, not slow.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-002-rca-analytics-revoked-grant.json

@@ -1545,7 +1545,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_rca_analytics_revoked_grant",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2464,5 +2464,5 @@
   },
   "task_id": "dob100-002-rca-analytics-revoked-grant",
   "task_name": "Analytics cannot read the replica since the rotation.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-003-rca-checkout-unschedulable-replicas.json

@@ -1547,7 +1547,7 @@
     "service": "checkout",
     "source_split": "train",
     "source_task_id": "tsk_rca_checkout_unschedulable_replicas",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2466,5 +2466,5 @@
   },
   "task_id": "dob100-003-rca-checkout-unschedulable-replicas",
   "task_name": "Checkout is running at a fraction of capacity.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-004-rca-media-disk-pressure.json

@@ -1545,7 +1545,7 @@
     "service": "media-service",
     "source_split": "train",
     "source_task_id": "tsk_rca_media_disk_pressure",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2464,5 +2464,5 @@
   },
   "task_id": "dob100-004-rca-media-disk-pressure",
   "task_name": "Media uploads stalling.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-005-rca-notifications-node-deadlock.json

@@ -1550,7 +1550,7 @@
     "service": "notifications",
     "source_split": "train",
     "source_task_id": "tsk_rca_notifications_node_deadlock",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2473,5 +2473,5 @@
   },
   "task_id": "dob100-005-rca-notifications-node-deadlock",
   "task_name": "Notifications are not being delivered.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-006-rca-search-unscheduled-reindex.json

@@ -1547,7 +1547,7 @@
     "service": "search",
     "source_split": "heldout",
     "source_task_id": "tsk_rca_search_unscheduled_reindex",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2468,5 +2468,5 @@
   },
   "task_id": "dob100-006-rca-search-unscheduled-reindex",
   "task_name": "Search results are stale.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-007-detect-checkout-errors.json

@@ -1545,7 +1545,7 @@
     "service": "checkout",
     "source_split": "train",
     "source_task_id": "tsk_detect_checkout_errors",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2456,5 +2456,5 @@
   },
   "task_id": "dob100-007-detect-checkout-errors",
   "task_name": "Is checkout violating its SLOs?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-008-detect-inventory.json

@@ -141,21 +141,21 @@
   },
   "assets": [
     {
-      "bytes": 872,
+      "bytes": 982,
       "evidence_role": "request",
       "kind": "md",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/01-employee-request.md",
-      "sha256": "8cfae4ec45ccae94b514865e1820d536dd4cee03387e972d8776f6b0f41e7d85",
+      "sha256": "3bbaf3e11bd78d3a111568d0298e844860d85e33e7a219dd640b2bc0e18de42f",
       "source": "employee request"
     },
     {
-      "bytes": 208,
+      "bytes": 205,
       "evidence_role": "identity",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/02-jira-work-item.csv",
-      "sha256": "5e0e13f1cae9c8278b42ff97cd8cea7768ab444abb8d732aadde31c690a1fb3e",
+      "sha256": "9bc59846b373280526dfa6a7e0544d78399d8711cb4b1ca54f5497cf5dc88c89",
       "source": "Atlassian Jira"
     },
     {
@@ -168,21 +168,21 @@
       "source": "tracker link registry"
     },
     {
-      "bytes": 190,
+      "bytes": 189,
       "evidence_role": "engineering-signal",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/04-github-issue.json",
-      "sha256": "18f207dd6677b4dce4bac3f99b305da52acb5141a7d5572ecdd1d3a55af2c7f5",
+      "sha256": "f7b65b5b2014ae50392cd3da97b1450d39c70fc74c4742c746724e3489b9ff2e",
       "source": "GitHub"
     },
     {
-      "bytes": 1292,
+      "bytes": 1291,
       "evidence_role": "authority",
       "kind": "pdf",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/05-current-operating-control.pdf",
-      "sha256": "b2e5ba9d67ac5d69ce4d0d151b4669280af70a4ae6e4bacf7f0507479f33cf1e",
+      "sha256": "953cf9ff65784aa07355c61d2851c0bcabda301996b84ef055ccc9cf1664848c",
       "source": "Confluence current export"
     },
     {
@@ -195,21 +195,21 @@
       "source": "Confluence history export"
     },
     {
-      "bytes": 884,
+      "bytes": 878,
       "evidence_role": "conversation",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/07-case-room-thread.json",
-      "sha256": "a0f0b12552d2cadabd6f822beede8242fafbb7a207a41e8bb8168ede0b6c521c",
+      "sha256": "0b85dc61c6bf2556d9abaed67f4f337dc67389d5b31c9049bc4d5619b516d5fa",
       "source": "Slack"
     },
     {
-      "bytes": 235,
+      "bytes": 233,
       "evidence_role": "change-history",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/08-pagerduty-change-events.csv",
-      "sha256": "d4cf2229be3921f0c7b5048cee25afe7cc7f94281a2464b350945cbeeac33e8b",
+      "sha256": "2d36785f21e967bafec746865ee40099f0f252e039615e9656d4fabdd36762b2",
       "source": "PagerDuty"
     },
     {
@@ -218,16 +218,16 @@
       "kind": "xlsx",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/09-service-owner-register.xlsx",
-      "sha256": "19e0314db9f52a9d0563e597868e197f8e2c59b2f670b14612b22962f56569ae",
+      "sha256": "cffef6d6050ce4327cb6c0fb68e7683e8550b5d047d0d83ff5278c0dfd42fc62",
       "source": "Microsoft Graph workbook"
     },
     {
-      "bytes": 1699,
+      "bytes": 1700,
       "evidence_role": "schedule",
       "kind": "xlsx",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/10-release-calendar.xlsx",
-      "sha256": "c44226601f40430660773de50207eb8c666d8ecc0bdc19eb7bc8bf737db66405",
+      "sha256": "97e06506c76f870b4ffeee06dee626ffbbf9031a7dc9e59169814ad523b0e58d",
       "source": "Microsoft Graph workbook"
     },
     {
@@ -267,30 +267,30 @@
       "source": "service catalog"
     },
     {
-      "bytes": 144,
+      "bytes": 200,
       "evidence_role": "live-signal",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/15-slo-export.csv",
-      "sha256": "9bbe4e9bb4f34c0d3b927b4d06f8757f7cbad3ea800ef3d9bd9f2aa1d3aecf4a",
+      "sha256": "2d2f59064f7c4d2debb14b964e1a077284b69d80835d272a15ac9951eef66225",
       "source": "SLO platform"
     },
     {
-      "bytes": 142,
+      "bytes": 140,
       "evidence_role": "live-signal",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/16-metrics-export.csv",
-      "sha256": "b61cecfd2b8d5098e4e4ccd7bcc1947e91ebce43c4043609c1585488a9c59389",
+      "sha256": "f825aacafc4867e4a2398b07fbb764ee03a7749592a0e0d7684537f2a0d2888f",
       "source": "Prometheus"
     },
     {
-      "bytes": 238,
+      "bytes": 779,
       "evidence_role": "live-signal",
       "kind": "log",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/17-observability-log-slice.log",
-      "sha256": "38a683bd3c63b00ece90b82564acc6d24dde89be1132772eaddd40cb868902d8",
+      "sha256": "9c94e2b5a7e2f9b3a8aec1adec4c1edc5a5b0ac8db21237a05010f574ae9a1de",
       "source": "log platform"
     },
     {
@@ -303,12 +303,12 @@
       "source": "Sentry"
     },
     {
-      "bytes": 662,
+      "bytes": 555,
       "evidence_role": "runtime-state",
       "kind": "yaml",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/19-kubernetes-pods.yaml",
-      "sha256": "47a592ab6671c9a26188aa1d32df18d65e8321dc64eef2383c2674f9abc5f328",
+      "sha256": "7b343d5f4cdfc7e887994c6601d092b370086a8328e41910e710c82cbd5070c0",
       "source": "Kubernetes"
     },
     {
@@ -321,21 +321,21 @@
       "source": "Kubernetes"
     },
     {
-      "bytes": 429,
+      "bytes": 427,
       "evidence_role": "deployment-state",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/21-deployment-history.json",
-      "sha256": "28db543c4d806fd50b1a3b0460111d03f397f5ab1e71451f2ba43be7f6a64e81",
+      "sha256": "2eb28632470c6f561be2f3cd2dd7eb56c2938c2db6b9a1a40b59bcbff7ca5c13",
       "source": "deployment platform"
     },
     {
-      "bytes": 185,
+      "bytes": 187,
       "evidence_role": "build-state",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/22-ci-runs.csv",
-      "sha256": "cf75fa78a75e44baa29016a53754e59f4acfce87cfaed1858e02b7016d8ce19c",
+      "sha256": "7250f53736011cd7e2f56081325708d15d2c018b36472e30d6606468b22e7f89",
       "source": "CI platform"
     },
     {
@@ -348,21 +348,21 @@
       "source": "GitHub"
     },
     {
-      "bytes": 279,
+      "bytes": 281,
       "evidence_role": "change-control",
       "kind": "sql",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/24-migration-state.sql",
-      "sha256": "d8aaef012a64e7d18f862e49788127d6b0d9fff04b8c3c3b86d4898d28403d74",
+      "sha256": "089efaa6fbd420db93adaa89fcc35ddda1c65b31c59f811e49762a47c3c9f7fd",
       "source": "database change control"
     },
     {
-      "bytes": 669,
+      "bytes": 841,
       "evidence_role": "security",
       "kind": "pdf",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/25-security-scanner-report.pdf",
-      "sha256": "2212cab0a5f5fc2af5678bf4d95d748f057d5e23e65f85cb02bf241e00fc923c",
+      "sha256": "dc34040e8e49c9b4795f23c3c62b8eee62344fda33e02edb096ec742fc50a8e0",
       "source": "security scanner"
     },
     {
@@ -384,52 +384,52 @@
       "source": "evidence custodian"
     },
     {
-      "bytes": 2663,
+      "bytes": 2660,
       "evidence_role": "capacity requirement",
       "kind": "pdf",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/28-change-readiness-standard.pdf",
-      "sha256": "e9622e135b1d405f1a1a277468157d129d26e24c31238516cd45358fc334dab3",
+      "sha256": "bfddbd231bb0a1456e2273371d057be64f133b2e86c72ecd90393f4b1a196677",
       "source": "Confluence current export"
     },
     {
-      "bytes": 313,
+      "bytes": 311,
       "evidence_role": "vendor lead time and cost",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/29-vendor-capacity-order.csv",
-      "sha256": "c1b4a52bea04959a92e314216b8a38863d3bdf35afcdf19d8d83e30ba1c14ddc",
+      "sha256": "a6ca6bbe0291d2bd81f428c04b65d7bf062cfc5afedff6e2ac233f521da69515",
       "source": "Atlassian Jira vendor project"
     },
     {
-      "bytes": 399,
+      "bytes": 397,
       "evidence_role": "approval scope",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/30-change-approval-record.csv",
-      "sha256": "8b83d961dc76e521f75eb3100b1a418acb3879c3759ad48d0a0cbd07a4fe8433",
+      "sha256": "0552a055171dc98541bb1b31df990e53d79f722be8991d355d663dd4c9f367a2",
       "source": "Atlassian Jira change advisory"
     },
     {
-      "bytes": 411,
+      "bytes": 407,
       "evidence_role": "capacity exclusion",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/31-capacity-reservation-register.json",
-      "sha256": "c4e7d612e0f7571c141daf001ca74151aebe86d3f8d3bf03f62112c11fbf2511",
+      "sha256": "55fd54d516bfaff3e63df10443c8e78946bec2e9c24815e10c4e77e04b8a14d2",
       "source": "Linear"
     },
     {
-      "bytes": 261,
+      "bytes": 260,
       "evidence_role": "independent business need",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/32-customer-cutover-notice.json",
-      "sha256": "ec27ae7607ca849134d611ae3efaa901fc38943073b908a27338310c7b6466a7",
+      "sha256": "aafe224e8077b1c58d5a90c9267760791804e02e601c4c5f1f6d4ffb9e4340e1",
       "source": "public status page"
     },
     {
-      "bytes": 685,
+      "bytes": 682,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -438,7 +438,7 @@
       "query_scope": {
         "key": "DOB-008"
       },
-      "sha256": "6cdbab26decea451dca86170e38a6a4ddcf672411a697995f8138e6d6fb6fae7",
+      "sha256": "8e7ad870b5c145e6f245a191e4719ae7e95811711907e16af79a0043b557e030",
       "source": "the authoritative Jira work item"
     },
     {
@@ -455,21 +455,21 @@
       "source": "the cross-tracker link registry"
     },
     {
-      "bytes": 540,
+      "bytes": 538,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the linked GitHub issue population",
       "path": "task_files/dob100-008-detect-inventory/material/03-the-linked-github-issue-population.json",
       "query_scope": {
-        "repo": "novacart/inventory",
+        "repo": "novacart/checkout",
         "state": "open"
       },
-      "sha256": "9a142d746f600e4ada37b543b88c2e657df141d232ea6bb6c25959872545e796",
+      "sha256": "c24633b8974182c961ffe10ec2ac814bcfe506c46a704a9398eb5f50f06087fc",
       "source": "the linked GitHub issue population"
     },
     {
-      "bytes": 786,
+      "bytes": 785,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -479,11 +479,11 @@
         "query": "DOB-008",
         "space": "OPS"
       },
-      "sha256": "fa9c8369aa2cdc94854a6845dc9bb0bb18233e17745a3bc4b90c4e4492ea38fb",
+      "sha256": "6861d03c5f82972239c621ae780986725884653c4617593c34814d226c357b07",
       "source": "the operating-control index"
     },
     {
-      "bytes": 1085,
+      "bytes": 1084,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -492,7 +492,7 @@
       "query_scope": {
         "page_id": 10008
       },
-      "sha256": "7285fb83f1ea33858facc9121c3eacbaa629d45c50543b685ac43c35123128d2",
+      "sha256": "18e47afd932773d59413234940793cbbfb54822fe420e525ab4353651a2a815c",
       "source": "the exact control revision"
     },
     {
@@ -509,21 +509,21 @@
       "source": "the exact control revision"
     },
     {
-      "bytes": 1237,
+      "bytes": 1230,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the case-room conversation",
       "path": "task_files/dob100-008-detect-inventory/material/07-the-case-room-conversation.json",
       "query_scope": {
-        "channel": "case-008-inventory",
+        "channel": "case-008-checkout",
         "limit": 50
       },
-      "sha256": "840eb11670dddaa1da4abb8ed0cf3c5e23c2c38af0c6c77f9d4ec66bff84caf4",
+      "sha256": "3842a67fcc37d6224974109e68011c2be7337559e16ded9868e4616fb1f80aeb",
       "source": "the case-room conversation"
     },
     {
-      "bytes": 699,
+      "bytes": 697,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -533,7 +533,7 @@
         "pd_service_id": "PD-DOB-008",
         "since_day": 330
       },
-      "sha256": "f12fd1762d11f1485ca76e8235165bd4cb76f92dfd150eb75bccdfa1a6a51676",
+      "sha256": "73e91a88336e84dffc483dd07af6717af3f8a76aa3ca5b0d6fe7523ae09450d8",
       "source": "the PagerDuty change-event history"
     },
     {
@@ -550,16 +550,16 @@
       "source": "the current customer-status record"
     },
     {
-      "bytes": 548,
+      "bytes": 545,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
-      "material_reason": "current service measurements (inventory)",
+      "material_reason": "current service measurements (checkout)",
       "path": "task_files/dob100-008-detect-inventory/material/10-current-service-measurements.json",
       "query_scope": {
-        "service": "inventory"
+        "service": "checkout"
       },
-      "sha256": "73b1567a781c064e83b8993c9f53d83ff9108fc859f4af6ed1106c09c66cb9c9",
+      "sha256": "20ceeb0e28e11aeb8192a432ff109bc325e0759ced6621f6d5e20002617264f5",
       "source": "current service measurements"
     },
     {
@@ -576,20 +576,20 @@
       "source": "actual alert firings"
     },
     {
-      "bytes": 1054,
+      "bytes": 946,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
-      "material_reason": "live Kubernetes pod state (inventory)",
+      "material_reason": "live Kubernetes pod state (checkout)",
       "path": "task_files/dob100-008-detect-inventory/material/12-live-kubernetes-pod-state.json",
       "query_scope": {
-        "service": "inventory"
+        "service": "checkout"
       },
-      "sha256": "906bcd0be3c474b41190d241745fc80352e8d315d33eb3d4a0ae4c3fa0e9c820",
+      "sha256": "3a2cfeab2947f26226415446bdc59cc78e057a4da66cc0290e4067b97743db2d",
       "source": "live Kubernetes pod state"
     },
     {
-      "bytes": 655,
+      "bytes": 674,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -598,11 +598,11 @@
       "query_scope": {
         "key": "OPS-102"
       },
-      "sha256": "592d6cb944fc5a0011131ab09ba213547362f5f7aa3890aedfbdad7137e7736e",
+      "sha256": "685901369de1d3b20d0b0b195e55342af7277dcff9447d4da3dd4b9e8a9b1624",
       "source": "the employee work item"
     },
     {
-      "bytes": 2299,
+      "bytes": 2296,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -611,11 +611,11 @@
       "query_scope": {
         "page_id": 14008
       },
-      "sha256": "be17591355c3484e463b2c3006b2da1f5f7df3462bdb77be3511e81e09044892",
+      "sha256": "5383d50e99eb90a451771756c1497e79e698d449f1ff90ab00012a6a6c97ccc0",
       "source": "the exact control revision"
     },
     {
-      "bytes": 713,
+      "bytes": 711,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -624,11 +624,11 @@
       "query_scope": {
         "key": "VEND-8"
       },
-      "sha256": "6fc6abc2b758ca7ecf2d9211a036ab066b76a2b1e6449db062fa77e933ca3233",
+      "sha256": "349191a5e47036596df85e805902be5171dd393c1a77eaaf50ed50e01c69bef5",
       "source": "the authoritative Jira work item"
     },
     {
-      "bytes": 800,
+      "bytes": 798,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -637,24 +637,24 @@
       "query_scope": {
         "key": "CHG-8"
       },
-      "sha256": "5e5c3eb84495a02db03934363b06da677ae1857f6598d9e045d8f24907f76b9d",
+      "sha256": "36cc5e996bd1109f9e00f986285920316df2867218002c8c479f72f962bf7b88",
       "source": "the authoritative Jira work item"
     },
     {
-      "bytes": 651,
+      "bytes": 646,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the linked planning tracker",
       "path": "task_files/dob100-008-detect-inventory/material/17-the-linked-planning-tracker.json",
       "query_scope": {
-        "team": "team-inventory"
+        "team": "team-checkout"
       },
-      "sha256": "fe3d58ca34356f32e84cd3737720e1e343fe17ea9b2429c66028c4c088c48c03",
+      "sha256": "bbb8a2b854678c3d6312b0aa61162df88b46289fcd7d434eeabbd8a345d443f1",
       "source": "the linked planning tracker"
     },
     {
-      "bytes": 1084,
+      "bytes": 1083,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -663,18 +663,18 @@
       "query_scope": {
         "since_day": 330
       },
-      "sha256": "b850d1bf2061d083de7a6cbf135af0a6b19385c174ec93312e6039730ce4b591",
+      "sha256": "2145a0dd0eeb9d966f679f610c9a2c40de32ecccc43fc37b62404f64f2e0b7ed",
       "source": "customer-status history"
     },
     {
-      "bytes": 1534,
+      "bytes": 1531,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current owner register",
       "path": "task_files/dob100-008-detect-inventory/material/19-the-current-owner-register.json",
       "query_scope": {},
-      "sha256": "9dbaf37979e97197185c6364ab800026ba1bcbbc6aeae3f029f6eb925d70208e",
+      "sha256": "def688f3a0e11925db473c933467a378d3a4f9c1807acfb282387f11c8616f3e",
       "source": "the current owner register"
     },
     {
@@ -689,12 +689,12 @@
       "source": "the PagerDuty service catalog"
     },
     {
-      "bytes": 18293,
+      "bytes": 18285,
       "evidence_role": "manifest",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-008-detect-inventory/51-agent-visible-asset-manifest.json",
-      "sha256": "e8dd88fd1afe21b8fba906b46972785eb6fe31c307721be85b54e1092d68d570",
+      "sha256": "7961ce1f809d7c9596790ac0dfeba65371ad1b3d3728cd4f5bc54b1405809483",
       "source": "release builder"
     }
   ],
@@ -781,7 +781,7 @@
       },
       {
         "check_id": "correctness.v5_answer_required_replicas",
-        "description": "Derived 4 per zone x 4 zones = 16 replicas required before the inventory cutover.",
+        "description": "Derived 4 per zone x 4 zones = 16 replicas required before the checkout cutover.",
         "field": "required_replicas",
         "id": "derive_plan_requirement",
         "milestone_id": "analysis.capacity_plan",
@@ -789,7 +789,7 @@
       },
       {
         "check_id": "correctness.v5_answer_observed_replicas",
-        "description": "Read 16 replicas in the inventory production pool from the PagerDuty scale record.",
+        "description": "Read 16 replicas in the checkout production pool from the PagerDuty scale record.",
         "field": "observed_replicas",
         "id": "read_gross_coverage",
         "milestone_id": "analysis.capacity_plan",
@@ -797,7 +797,7 @@
       },
       {
         "check_id": "correctness.v5_answer_reserved_replicas",
-        "description": "Excluded 2 replicas reserved for the api-gateway freeze in Linear CAP-8.",
+        "description": "Excluded 2 replicas reserved for the inventory freeze in Linear CAP-8.",
         "field": "reserved_replicas",
         "id": "remove_ineligible_coverage",
         "milestone_id": "analysis.capacity_plan",
@@ -853,7 +853,7 @@
       },
       {
         "check_id": "correctness.v5_answer_next_change_window",
-        "description": "Read the inventory change calendar (2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10) from the current operating control and identified 2026-03-04 as the next window.",
+        "description": "Read the checkout change calendar (2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10) from the current operating control and identified 2026-03-04 as the next window.",
         "field": "next_change_window",
         "id": "identify_safe_window",
         "milestone_id": "analysis.capacity_plan",
@@ -944,12 +944,12 @@
     "facts": [
       {
         "id": "authoritative_identity",
-        "rubric": "Located DOB-008 for inventory through immutable Jira and GitHub identities and preserved OPS-CONTROL-2026.03 as the effective control.",
+        "rubric": "Located DOB-008 for checkout through immutable Jira and GitHub identities and preserved OPS-CONTROL-2026.03 as the effective control.",
         "sources": [
           "jira",
           "github"
         ],
-        "statement": "DOB-008 resolves to Jira DOB-008 and GitHub issue #9008 for inventory; the effective control is OPS-CONTROL-2026.03."
+        "statement": "DOB-008 resolves to Jira DOB-008 and GitHub issue #9008 for checkout; the effective control is OPS-CONTROL-2026.03."
       },
       {
         "id": "effective_requirement",
@@ -967,7 +967,7 @@
           "pagerduty",
           "linear"
         ],
-        "statement": "The pool holds 16 replicas; 2 are reserved for the api-gateway freeze, leaving 14 usable and a gap of 2."
+        "statement": "The pool holds 16 replicas; 2 are reserved for the inventory freeze, leaving 14 usable and a gap of 2."
       },
       {
         "id": "conditional_external_recovery",
@@ -979,11 +979,11 @@
       },
       {
         "id": "finite_capacity",
-        "rubric": "Applied the published inventory change calendar to derive every plan's completion without using excluded or unapproved scope.",
+        "rubric": "Applied the published checkout change calendar to derive every plan's completion without using excluded or unapproved scope.",
         "sources": [
           "confluence"
         ],
-        "statement": "Change windows for inventory are 2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10; work outside a window needs incident-commander approval."
+        "statement": "Change windows for checkout are 2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10; work outside a window needs incident-commander approval."
       },
       {
         "id": "approval_scope",
@@ -1028,7 +1028,7 @@
       {
         "approval": "ADDITIONAL_APPROVAL_REQUIRED",
         "completion": "2026-03-03",
-        "consequence": "Releasing the 2 replicas reserved for the api-gateway freeze would cover the 2-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-8, and adds the USD 1800 re-provisioning charge.",
+        "consequence": "Releasing the 2 replicas reserved for the inventory freeze would cover the 2-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-8, and adds the USD 1800 re-provisioning charge.",
         "control_status": "SEPARATE_APPROVAL_OR_POLICY_EXCEPTION_REQUIRED",
         "id": "release_reserved_capacity",
         "incremental_cost": 1800,
@@ -1042,7 +1042,7 @@
     "selected_completion": "2026-03-04",
     "selected_option": "expedite_capacity",
     "source_document": "DOB-008 change-readiness standard, CloudCap order VEND-8, change approval CHG-8",
-    "subject": "inventory customer cutover readiness for DOB-008"
+    "subject": "checkout customer cutover readiness for DOB-008"
   },
   "expected": {
     "answer": {
@@ -1258,7 +1258,7 @@
     ]
   },
   "gold_output": {
-    "atomic_check_count": 58,
+    "atomic_check_count": 69,
     "expected_semantic_milestones": [
       {
         "id": "investigation.scope",
@@ -1328,7 +1328,7 @@
     "ground_truth_submissions": [
       {
         "arguments": {
-          "evidence": "inventory error_rate_pct is 4.7 against a 1.0 SLO; alarm 9606 is firing",
+          "evidence": "inventory error_rate_pct is 4.7 against a 1.0 SLO; the 5-connection pool is exhausted by 128 reservation requests per second across 12 pods",
           "fault_detected": true,
           "fault_type": "resource_exhaustion",
           "offending_key": "db_pool_size",
@@ -1356,7 +1356,7 @@
     ],
     "note": "Acceptance is causal and state-based: all semantic milestones must hold over successful material reads, provider state, post-write readback, the append-only audit log, and write-scope containment."
   },
-  "instruction_guided": "This is an investigation, not a change. Do NOT modify production state: no pull requests, deploys, flag toggles, migrations or resolutions. Investigate with the read tools and report what you find with submit_diagnosis(...).\n\nOPS-102 — Detection: is inventory violating its SLOs?\n\nDetermine whether inventory is currently violating any of its service level objectives, and submit the result under scope 'inventory' with the evidence you relied on. Report honestly either way: a clean bill of health is a valid finding.\n\nProcedure: compare live production metrics against the service's SLOs and check the alarm state, then submit. If healthy, submit fault_detected=false with fault_type='none'.",
+  "instruction_guided": "This is an investigation, not a change. Do NOT modify production state: no pull requests, deploys, flag toggles, migrations or resolutions. Investigate with the read tools and report what you find with submit_diagnosis(...).\n\nOPS-102 — Determine whether reservation failures are a capacity incident\n\nWarehouse reservations are timing out during the morning order wave. The alert names inventory, but Operations needs to know whether this is a real capacity failure, where the bottleneck sits, and which setting controls it before changing the production plan.\n\nWork out which service this is about, determine whether it is currently violating any of its service level objectives, and submit the result under scope 'inventory' — naming the service in the `service` field — with the evidence you relied on. Report honestly either way: a clean bill of health is a valid finding, and so is contradicting a system that says everything is fine. If it is real, identify the mechanism and exact controlling setting; do not stop at restating the alert.\n\nProcedure: compare live production metrics against the service's SLOs and check the alarm state, then submit. If healthy, submit fault_detected=false with fault_type='none'.",
   "metadata": {
     "benchmark": "DevOpsBench-100",
     "business_reasoning_primitives": [
@@ -1378,14 +1378,14 @@
     "curation_rationale": [
       "aiops_detection",
       "easy",
-      "6-call-oracle",
+      "14-call-oracle",
       "curated",
       "hardest-of-category-quota",
       "controls-rejected:pristine"
     ],
     "data_license": "CC-BY-4.0",
     "decision_mode": "capacity_plan",
-    "difficulty": "easy",
+    "difficulty": "hard",
     "graded_answer_fields": 23,
     "grading": "deterministic",
     "guided_instruction_available": true,
@@ -1428,12 +1428,12 @@
       "cross-tracker link registry"
     ],
     "reasoning_contract": {
-      "change_or_record": "Establish the exact business state for “Is inventory violating its SLOs?”: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Coordinate the linked records for “Is inventory violating its SLOs?”: close ticket OPS-102 once reported. Keep “Is inventory violating its SLOs?” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
-      "decide": "Choose the branch for “Is inventory violating its SLOs?” that can legitimately produce this business state: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Is inventory violating its SLOs?” through inventory: standard capacity finishes 2026-03-08 at USD 0; expedited capacity finishes 2026-03-04 at USD 750; releasing reserved capacity finishes 2026-03-03 at USD 1800 but requires approval beyond CHG-8. Recommend expedite_capacity, record its 2026-03-04 outcome and -1-day variance, and report ON_TIME honestly.",
-      "deliver": "Leave the employee-facing conclusion for “Is inventory violating its SLOs?” with the exact supported insight: record whether inventory has an active objective breach; inventory is breaching its SLO: the final finding must record an active fault; record the evidence that supports the finding; write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (expedite_capacity) in the scoped completion handoff; state the outcome date (2026-03-04) in the scoped completion handoff; state the approval reference (CHG-8) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap expedited capacity on 2026-03-04) in the scoped completion handoff. Close “Is inventory violating its SLOs?” only after the business state and readbacks are complete: close OPS-102 only once the finding is submitted, not before.",
-      "employee_outcome": "Is inventory violating its SLOs?",
-      "investigate": "Build the causal case for “Is inventory violating its SLOs?”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the PagerDuty change-event history, and the current customer-status record; finally test the competing explanation against current service measurements (inventory), actual alert firings, live Kubernetes pod state (inventory), and the employee work item. All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Preserve this additional control: an investigation must not change production state. Prove that the same outcome for “Is inventory violating its SLOs?” is deliverable through inventory, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 16 observed less 2 reserved for api-gateway leaves 14 usable and a 2-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-05 customer date.",
-      "verify": "Prove the observable result for “Is inventory violating its SLOs?” after the transition: reopen the employee work item and confirm the persisted result. After the last guarded transition for “Is inventory violating its SLOs?”, reopen the employee work item, then reopen the completion conversation so persistence and communication are both proven."
+      "change_or_record": "Establish the exact business state for “Determine whether reservation failures are a capacity incident.”: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Coordinate the linked records for “Determine whether reservation failures are a capacity incident.”: close ticket OPS-102 once reported. Keep “Determine whether reservation failures are a capacity incident.” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
+      "decide": "Choose the branch for “Determine whether reservation failures are a capacity incident.” that can legitimately produce this business state: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Determine whether reservation failures are a capacity incident.” through checkout: standard capacity finishes 2026-03-08 at USD 0; expedited capacity finishes 2026-03-04 at USD 750; releasing reserved capacity finishes 2026-03-03 at USD 1800 but requires approval beyond CHG-8. Recommend expedite_capacity, record its 2026-03-04 outcome and -1-day variance, and report ON_TIME honestly.",
+      "deliver": "Leave the employee-facing conclusion for “Determine whether reservation failures are a capacity incident.” with the exact supported insight: record whether inventory has an active objective breach; inventory is breaching its SLO: the final finding must record an active fault; record the evidence that supports the finding; write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (expedite_capacity) in the scoped completion handoff; state the outcome date (2026-03-04) in the scoped completion handoff; state the approval reference (CHG-8) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap expedited capacity on 2026-03-04) in the scoped completion handoff. Close “Determine whether reservation failures are a capacity incident.” only after the business state and readbacks are complete: close OPS-102 only once the finding is submitted, not before.",
+      "employee_outcome": "Determine whether reservation failures are a capacity incident.",
+      "investigate": "Build the causal case for “Determine whether reservation failures are a capacity incident.”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the PagerDuty change-event history, and the current customer-status record; finally test the competing explanation against current service measurements (checkout), actual alert firings, live Kubernetes pod state (checkout), and the employee work item. All 20 exact causal facts must be present inside the 32-read investigation before they support this outcome: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Preserve this additional control: identify the supported fault mechanism as resource_exhaustion; an investigation must not change production state. Prove that the same outcome for “Determine whether reservation failures are a capacity incident.” is deliverable through checkout, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 16 observed less 2 reserved for inventory leaves 14 usable and a 2-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-05 customer date.",
+      "verify": "Prove the observable result for “Determine whether reservation failures are a capacity incident.” after the transition: reopen the employee work item and confirm the persisted result. After the last guarded transition for “Determine whether reservation failures are a capacity incident.”, reopen the employee work item, then reopen the completion conversation so persistence and communication are both proven."
     },
     "reference_assets": [
       "task_files/dob100-008-detect-inventory/01-employee-request.md",
@@ -1490,8 +1490,8 @@
       "task_files/dob100-008-detect-inventory/material/20-the-pagerduty-service-catalog.json",
       "task_files/dob100-008-detect-inventory/51-agent-visible-asset-manifest.json"
     ],
-    "reference_evidence_reads": 26,
-    "reference_tool_calls": 32,
+    "reference_evidence_reads": 32,
+    "reference_tool_calls": 38,
     "reference_tools": [
       "jira_get_issue",
       "list_issue_links",
@@ -1510,21 +1510,32 @@
       "read_owner_spreadsheet",
       "pd_list_services",
       "jira_search",
+      "get_service",
+      "list_infra",
+      "get_traffic_stats",
+      "search_logs",
+      "list_error_events",
+      "read_file",
+      "list_commits",
       "get_slo_status",
       "list_alerts",
-      "resolve_service_alias",
-      "pd_list_oncalls",
-      "list_alert_rules",
       "submit_diagnosis",
       "update_ticket",
       "submit_answer",
       "post_message"
     ],
     "required_tools": [
+      "get_service",
       "get_slo_status",
       "get_ticket",
+      "get_traffic_stats",
       "list_alerts",
+      "list_commits",
+      "list_error_events",
+      "list_infra",
       "query_metrics",
+      "read_file",
+      "search_logs",
       "submit_diagnosis",
       "update_ticket"
     ],
@@ -1537,15 +1548,15 @@
       "derive_detect_supported_branch",
       "execute_submit_diagnosis",
       "execute_update_ticket",
-      "plan_inventory_cutover_capacity_expedite_capacity",
+      "plan_checkout_cutover_capacity_expedite_capacity",
       "reconcile_detect_post_change_state",
       "handoff_source_backed_result_to_owner",
       "reopen_persisted_state_and_conversation"
     ],
-    "service": "inventory",
+    "service": "checkout",
     "source_split": "train",
     "source_task_id": "tsk_detect_inventory",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -1564,7 +1575,7 @@
       "milestone_id": "verification.outcome"
     }
   ],
-  "prompt": "Is inventory violating its SLOs? The current monitoring views do not yet establish whether this is an active objective breach, a stale signal, or a healthy service being blamed for a downstream symptom. For inventory, the affected business boundary includes stock reservation, warehouse truth, backorder promises, and race-free quantity updates. Reconcile the affected boundary, identify the decisive signal, and record a production-safe conclusion the service owner can use in the existing incident work item. The supported cause controls whether inventory can enter the recovery window on 2026-03-05, making this one incident decision rather than a separate planning exercise. State the earliest credible completion and whether it meets the business window. Include the best approved path and the faster or cheaper alternatives that the evidence or authority rules out.",
+  "prompt": "Determine whether reservation failures are a capacity incident. The current monitoring views do not yet establish whether this is an active objective breach, a stale signal, or a healthy service being blamed for a downstream symptom. For inventory → checkout capability chain, the affected business boundary includes the upstream-to-downstream dependency direction, the contract at each service boundary, ownership, recoverability, and end-to-end health. Reconcile the affected boundary, identify the decisive signal, and record a production-safe conclusion the service owner can use in the existing incident work item. The supported cause controls whether checkout can enter the recovery window on 2026-03-05, making this one incident decision rather than a separate planning exercise. State the earliest credible completion and whether it meets the business window. Include the best approved path and the faster or cheaper alternatives that the evidence or authority rules out.",
   "required_investigations": [
     {
       "any_of": [
@@ -1602,7 +1613,7 @@
       "any_of": [
         {
           "arguments": {
-            "repo": "novacart/inventory",
+            "repo": "novacart/checkout",
             "state": "open"
           },
           "tool": "github_list_issues"
@@ -1610,7 +1621,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_case_identity_resolved",
-      "description": "Located GitHub issue #9008 in novacart/inventory by immutable number.",
+      "description": "Located GitHub issue #9008 in novacart/checkout by immutable number.",
       "group": "identity",
       "id": "investigation_03",
       "milestone_id": "investigation.scope"
@@ -1643,7 +1654,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_authority_reconciled",
-      "description": "Applied OPS-CONTROL-2026.03 and its inventory change windows: 2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10.",
+      "description": "Applied OPS-CONTROL-2026.03 and its checkout change windows: 2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10.",
       "group": "authority",
       "id": "investigation_05",
       "milestone_id": "investigation.authority"
@@ -1668,7 +1679,7 @@
       "any_of": [
         {
           "arguments": {
-            "channel": "case-008-inventory",
+            "channel": "case-008-checkout",
             "limit": 50
           },
           "tool": "list_messages"
@@ -1676,7 +1687,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Separated the case-room business request from formal operational authority for inventory.",
+      "description": "Separated the case-room business request from formal operational authority for checkout.",
       "group": "ownership_and_conversation",
       "id": "investigation_07",
       "milestone_id": "analysis.causal_reasoning"
@@ -1693,7 +1704,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Read the live inventory pool record: 16 replicas across 4 zones.",
+      "description": "Read the live checkout pool record: 16 replicas across 4 zones.",
       "group": "ownership_and_conversation",
       "id": "investigation_08",
       "milestone_id": "analysis.causal_reasoning"
@@ -1709,7 +1720,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Correlated the live inventory get_status_page record that controls the aiops_detection decision.",
+      "description": "Correlated the live checkout get_status_page record that controls the aiops_detection decision.",
       "group": "ownership_and_conversation",
       "id": "investigation_09",
       "milestone_id": "analysis.causal_reasoning"
@@ -1718,14 +1729,14 @@
       "any_of": [
         {
           "arguments": {
-            "service": "inventory"
+            "service": "checkout"
           },
           "tool": "query_metrics"
         }
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live inventory query_metrics record that controls the aiops_detection decision.",
+      "description": "Correlated the live checkout query_metrics record that controls the aiops_detection decision.",
       "group": "live_state",
       "id": "investigation_10",
       "milestone_id": "investigation.live_state"
@@ -1741,7 +1752,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live inventory list_alert_firings record that controls the aiops_detection decision.",
+      "description": "Correlated the live checkout list_alert_firings record that controls the aiops_detection decision.",
       "group": "live_state",
       "id": "investigation_11",
       "milestone_id": "investigation.live_state"
@@ -1750,14 +1761,14 @@
       "any_of": [
         {
           "arguments": {
-            "service": "inventory"
+            "service": "checkout"
           },
           "tool": "k8s_pods_list"
         }
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live inventory k8s_pods_list record that controls the aiops_detection decision.",
+      "description": "Correlated the live checkout k8s_pods_list record that controls the aiops_detection decision.",
       "group": "live_state",
       "id": "investigation_12",
       "milestone_id": "investigation.live_state"
@@ -1773,7 +1784,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live inventory get_ticket record that controls the aiops_detection decision.",
+      "description": "Correlated the live checkout get_ticket record that controls the aiops_detection decision.",
       "group": "live_state",
       "id": "investigation_13",
       "milestone_id": "investigation.live_state"
@@ -1789,7 +1800,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v5_capacity_evidence_complete",
-      "description": "Established the inventory requirement of 4 healthy replicas in each production zone.",
+      "description": "Established the checkout requirement of 4 healthy replicas in each production zone.",
       "group": "capacity_plan",
       "id": "investigation_14",
       "milestone_id": "analysis.capacity_plan"
@@ -1830,14 +1841,14 @@
       "any_of": [
         {
           "arguments": {
-            "team": "team-inventory"
+            "team": "team-checkout"
           },
           "tool": "linear_list_issues"
         }
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v5_capacity_evidence_complete",
-      "description": "Excluded 2 replicas reserved for the api-gateway freeze.",
+      "description": "Excluded 2 replicas reserved for the inventory freeze.",
       "group": "capacity_plan",
       "id": "investigation_17",
       "milestone_id": "analysis.capacity_plan"
@@ -1867,7 +1878,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Confirmed the accountable inventory owner and scoped case channel.",
+      "description": "Confirmed the accountable checkout owner and scoped case channel.",
       "group": "corroborating_context",
       "id": "investigation_19",
       "milestone_id": "analysis.causal_reasoning"
@@ -1881,7 +1892,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Correlated the live inventory pd_list_services record that controls the aiops_detection decision.",
+      "description": "Correlated the live checkout pd_list_services record that controls the aiops_detection decision.",
       "group": "corroborating_context",
       "id": "investigation_20",
       "milestone_id": "analysis.causal_reasoning"
@@ -1917,7 +1928,7 @@
           }
         ],
         "category": "investigation",
-        "description": "Treat “Is inventory violating its SLOs?” as one immutable cross-system work item: correlate its Jira record to the linked GitHub evidence and exclude neighboring work that merely shares a name.",
+        "description": "Treat “Determine whether reservation failures are a capacity incident.” as one immutable cross-system work item: correlate its Jira record to the linked GitHub evidence and exclude neighboring work that merely shares a name.",
         "id": "investigation.scope",
         "weight": 5
       },
@@ -1931,26 +1942,32 @@
           }
         ],
         "category": "investigation",
-        "description": "Use OPS-CONTROL-2026.03 as the operative control and treat OPS-CONTROL-2025.11 as a conflicting historical shortcut before deciding “Is inventory violating its SLOs?”.",
+        "description": "Use OPS-CONTROL-2026.03 as the operative control and treat OPS-CONTROL-2025.11 as a conflicting historical shortcut before deciding “Determine whether reservation failures are a capacity incident.”.",
         "id": "investigation.authority",
         "weight": 5
       },
       {
         "atomic_checks": [
           {
-            "description": "correlate the task-specific inventory provider state instead of relying on files or tracker text alone",
+            "description": "correlate the task-specific checkout provider state instead of relying on files or tracker text alone",
             "dimension": "correctness",
             "id": "correctness.v4_live_state_correlated",
             "name": "v4_live_state_correlated"
           }
         ],
         "category": "investigation",
-        "description": "For “Is inventory violating its SLOs?”, interrogate current service measurements (inventory), actual alert firings, live Kubernetes pod state (inventory), and the employee work item; tracker prose and seeded files alone cannot establish the current answer.",
+        "description": "For “Determine whether reservation failures are a capacity incident.”, interrogate current service measurements (checkout), actual alert firings, live Kubernetes pod state (checkout), and the employee work item; tracker prose and seeded files alone cannot establish the current answer.",
         "id": "investigation.live_state",
         "weight": 7
       },
       {
         "atomic_checks": [
+          {
+            "description": "identify the supported fault mechanism as resource_exhaustion",
+            "dimension": "correctness",
+            "id": "correctness.fault_type_identified",
+            "name": "fault_type_identified"
+          },
           {
             "description": "an investigation must not change production state",
             "dimension": "deployment",
@@ -1965,7 +1982,7 @@
           }
         ],
         "category": "analysis",
-        "description": "Build the causal case for “Is inventory violating its SLOs?”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the PagerDuty change-event history, and the current customer-status record; finally test the competing explanation against current service measurements (inventory), actual alert firings, live Kubernetes pod state (inventory), and the employee work item. All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Preserve this additional control: an investigation must not change production state.",
+        "description": "Build the causal case for “Determine whether reservation failures are a capacity incident.”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the PagerDuty change-event history, and the current customer-status record; finally test the competing explanation against current service measurements (checkout), actual alert firings, live Kubernetes pod state (checkout), and the employee work item. All 20 exact causal facts must be present inside the 32-read investigation before they support this outcome: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Preserve this additional control: identify the supported fault mechanism as resource_exhaustion; an investigation must not change production state.",
         "id": "analysis.causal_reasoning",
         "weight": 6
       },
@@ -1990,19 +2007,19 @@
             "name": "v5_answer_production_zones"
           },
           {
-            "description": "Derived 4 per zone x 4 zones = 16 replicas required before the inventory cutover.",
+            "description": "Derived 4 per zone x 4 zones = 16 replicas required before the checkout cutover.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_required_replicas",
             "name": "v5_answer_required_replicas"
           },
           {
-            "description": "Read 16 replicas in the inventory production pool from the PagerDuty scale record.",
+            "description": "Read 16 replicas in the checkout production pool from the PagerDuty scale record.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_observed_replicas",
             "name": "v5_answer_observed_replicas"
           },
           {
-            "description": "Excluded 2 replicas reserved for the api-gateway freeze in Linear CAP-8.",
+            "description": "Excluded 2 replicas reserved for the inventory freeze in Linear CAP-8.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_reserved_replicas",
             "name": "v5_answer_reserved_replicas"
@@ -2044,7 +2061,7 @@
             "name": "v5_answer_capacity_request_replicas"
           },
           {
-            "description": "Read the inventory change calendar (2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10) from the current operating control and identified 2026-03-04 as the next window.",
+            "description": "Read the checkout change calendar (2026-03-04, 2026-03-06, 2026-03-08, 2026-03-10) from the current operating control and identified 2026-03-04 as the next window.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_next_change_window",
             "name": "v5_answer_next_change_window"
@@ -2057,7 +2074,7 @@
           }
         ],
         "category": "analysis",
-        "description": "Prove that the same outcome for “Is inventory violating its SLOs?” is deliverable through inventory, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 16 observed less 2 reserved for api-gateway leaves 14 usable and a 2-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-05 customer date.",
+        "description": "Prove that the same outcome for “Determine whether reservation failures are a capacity incident.” is deliverable through checkout, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 16 observed less 2 reserved for inventory leaves 14 usable and a 2-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-05 customer date.",
         "id": "analysis.capacity_plan",
         "weight": 9
       },
@@ -2071,7 +2088,7 @@
           }
         ],
         "category": "decision",
-        "description": "Choose the branch for “Is inventory violating its SLOs?” that can legitimately produce this business state: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Reject a stale-record shortcut, an unsupported hold, and any broader workaround.",
+        "description": "Choose the branch for “Determine whether reservation failures are a capacity incident.” that can legitimately produce this business state: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Reject a stale-record shortcut, an unsupported hold, and any broader workaround.",
         "id": "decision.supported_path",
         "weight": 5
       },
@@ -2151,12 +2168,72 @@
           }
         ],
         "category": "decision",
-        "description": "Compare three concrete, linked readiness options for “Is inventory violating its SLOs?” through inventory: standard capacity finishes 2026-03-08 at USD 0; expedited capacity finishes 2026-03-04 at USD 750; releasing reserved capacity finishes 2026-03-03 at USD 1800 but requires approval beyond CHG-8. Recommend expedite_capacity, record its 2026-03-04 outcome and -1-day variance, and report ON_TIME honestly.",
+        "description": "Compare three concrete, linked readiness options for “Determine whether reservation failures are a capacity incident.” through checkout: standard capacity finishes 2026-03-08 at USD 0; expedited capacity finishes 2026-03-04 at USD 750; releasing reserved capacity finishes 2026-03-03 at USD 1800 but requires approval beyond CHG-8. Recommend expedite_capacity, record its 2026-03-04 outcome and -1-day variance, and report ON_TIME honestly.",
         "id": "decision.options",
         "weight": 8
       },
       {
         "atomic_checks": [
+          {
+            "description": "the service behind the symptom is inventory",
+            "dimension": "correctness",
+            "id": "correctness.service_identified",
+            "name": "service_identified"
+          },
+          {
+            "description": "identify db_pool_size as the controlling setting",
+            "dimension": "correctness",
+            "id": "correctness.controlling_setting_identified",
+            "name": "controlling_setting_identified"
+          },
+          {
+            "description": "the causal investigation must use get_service before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_01_get_service",
+            "name": "causal_read_01_get_service"
+          },
+          {
+            "description": "the causal investigation must use get_service before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_02_get_service",
+            "name": "causal_read_02_get_service"
+          },
+          {
+            "description": "the causal investigation must use list_infra before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_03_list_infra",
+            "name": "causal_read_03_list_infra"
+          },
+          {
+            "description": "the causal investigation must use get_traffic_stats before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_04_get_traffic_stats",
+            "name": "causal_read_04_get_traffic_stats"
+          },
+          {
+            "description": "the causal investigation must use search_logs before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_05_search_logs",
+            "name": "causal_read_05_search_logs"
+          },
+          {
+            "description": "the causal investigation must use list_error_events before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_06_list_error_events",
+            "name": "causal_read_06_list_error_events"
+          },
+          {
+            "description": "the causal investigation must use read_file before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_07_read_file",
+            "name": "causal_read_07_read_file"
+          },
+          {
+            "description": "the causal investigation must use list_commits before submitting the diagnosis",
+            "dimension": "correctness",
+            "id": "correctness.causal_read_08_list_commits",
+            "name": "causal_read_08_list_commits"
+          },
           {
             "description": "complete each task-required state-changing capability at least once successfully",
             "dimension": "correctness",
@@ -2165,7 +2242,7 @@
           }
         ],
         "category": "state",
-        "description": "Establish the exact business state for “Is inventory violating its SLOs?”: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done.",
+        "description": "Establish the exact business state for “Determine whether reservation failures are a capacity incident.”: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis.",
         "id": "state.primary",
         "weight": 14
       },
@@ -2179,7 +2256,7 @@
           }
         ],
         "category": "state",
-        "description": "Coordinate the linked records for “Is inventory violating its SLOs?”: close ticket OPS-102 once reported.",
+        "description": "Coordinate the linked records for “Determine whether reservation failures are a capacity incident.”: close ticket OPS-102 once reported.",
         "id": "state.coordination",
         "weight": 6
       },
@@ -2193,7 +2270,7 @@
           }
         ],
         "category": "verification",
-        "description": "Prove the observable result for “Is inventory violating its SLOs?” after the transition: reopen the employee work item and confirm the persisted result.",
+        "description": "Prove the observable result for “Determine whether reservation failures are a capacity incident.” after the transition: reopen the employee work item and confirm the persisted result.",
         "id": "verification.outcome",
         "weight": 7
       },
@@ -2213,7 +2290,7 @@
           }
         ],
         "category": "verification",
-        "description": "After the last guarded transition for “Is inventory violating its SLOs?”, reopen the employee work item, then reopen the completion conversation so persistence and communication are both proven.",
+        "description": "After the last guarded transition for “Determine whether reservation failures are a capacity incident.”, reopen the employee work item, then reopen the completion conversation so persistence and communication are both proven.",
         "id": "verification.readback",
         "weight": 6
       },
@@ -2239,7 +2316,7 @@
           }
         ],
         "category": "execution",
-        "description": "Respect the causal order for “Is inventory violating its SLOs?”: derive the capacity plan only after every source fact it depends on has been read successfully; record the capacity plan before stating it in the completion handoff.",
+        "description": "Respect the causal order for “Determine whether reservation failures are a capacity incident.”: derive the capacity plan only after every source fact it depends on has been read successfully; record the capacity plan before stating it in the completion handoff.",
         "id": "execution.sequence",
         "weight": 6
       },
@@ -2265,7 +2342,7 @@
           }
         ],
         "category": "containment",
-        "description": "Keep “Is inventory violating its SLOs?” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
+        "description": "Keep “Determine whether reservation failures are a capacity incident.” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
         "id": "containment.scope",
         "weight": 7
       },
@@ -2333,14 +2410,14 @@
           }
         ],
         "category": "answer",
-        "description": "Leave the employee-facing conclusion for “Is inventory violating its SLOs?” with the exact supported insight: record whether inventory has an active objective breach; inventory is breaching its SLO: the final finding must record an active fault; record the evidence that supports the finding; write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (expedite_capacity) in the scoped completion handoff; state the outcome date (2026-03-04) in the scoped completion handoff; state the approval reference (CHG-8) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap expedited capacity on 2026-03-04) in the scoped completion handoff.",
+        "description": "Leave the employee-facing conclusion for “Determine whether reservation failures are a capacity incident.” with the exact supported insight: record whether inventory has an active objective breach; inventory is breaching its SLO: the final finding must record an active fault; record the evidence that supports the finding; write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (expedite_capacity) in the scoped completion handoff; state the outcome date (2026-03-04) in the scoped completion handoff; state the approval reference (CHG-8) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap expedited capacity on 2026-03-04) in the scoped completion handoff.",
         "id": "answer.insights",
         "weight": 4
       },
       {
         "atomic_checks": [
           {
-            "description": "reach a conclusion within 8 tool calls",
+            "description": "reach a conclusion within 16 tool calls",
             "dimension": "quality",
             "id": "quality.efficient_investigation",
             "name": "efficient_investigation"
@@ -2359,7 +2436,7 @@
           }
         ],
         "category": "execution",
-        "description": "Complete “Is inventory violating its SLOs?” without unsafe retries or unproductive loops: reach a conclusion within 8 tool calls; avoid repeated validation runs that make no progress.",
+        "description": "Complete “Determine whether reservation failures are a capacity incident.” without unsafe retries or unproductive loops: reach a conclusion within 16 tool calls; avoid repeated validation runs that make no progress.",
         "id": "execution.efficiency",
         "weight": 3
       },
@@ -2379,7 +2456,7 @@
           }
         ],
         "category": "execution",
-        "description": "Close “Is inventory violating its SLOs?” only after the business state and readbacks are complete: close OPS-102 only once the finding is submitted, not before.",
+        "description": "Close “Determine whether reservation failures are a capacity incident.” only after the business state and readbacks are complete: close OPS-102 only once the finding is submitted, not before.",
         "id": "execution.delivery",
         "weight": 2
       }
@@ -2412,12 +2489,12 @@
       {
         "approval": "ADDITIONAL_APPROVAL_REQUIRED",
         "completion": "2026-03-03",
-        "consequence": "Releasing the 2 replicas reserved for the api-gateway freeze would cover the 2-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-8, and adds the USD 1800 re-provisioning charge.",
+        "consequence": "Releasing the 2 replicas reserved for the inventory freeze would cover the 2-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-8, and adds the USD 1800 re-provisioning charge.",
         "control_status": "SEPARATE_APPROVAL_OR_POLICY_EXCEPTION_REQUIRED",
         "id": "release_reserved_capacity",
         "incremental_cost": 1800,
         "label": "release_reserved_capacity: outcome 2026-03-03, incremental cost USD 1800, SEPARATE_APPROVAL_OR_POLICY_EXCEPTION_REQUIRED",
-        "reason": "Releasing the 2 replicas reserved for the api-gateway freeze covers the gap today but needs approval beyond CHG-8. Releasing the 2 replicas reserved for the api-gateway freeze would cover the 2-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-8, and adds the USD 1800 re-provisioning charge.",
+        "reason": "Releasing the 2 replicas reserved for the inventory freeze covers the gap today but needs approval beyond CHG-8. Releasing the 2 replicas reserved for the inventory freeze would cover the 2-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-8, and adds the USD 1800 re-provisioning charge.",
         "recommended": false,
         "selected": false
       }
@@ -2426,12 +2503,12 @@
     "llm_judge": false,
     "pass_rule": "all 16 semantic milestones hold over causal tool evidence, the graded capacity-plan decision record, final world state, readback, and containment",
     "reasoning_contract": {
-      "change_or_record": "Establish the exact business state for “Is inventory violating its SLOs?”: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Coordinate the linked records for “Is inventory violating its SLOs?”: close ticket OPS-102 once reported. Keep “Is inventory violating its SLOs?” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
-      "decide": "Choose the branch for “Is inventory violating its SLOs?” that can legitimately produce this business state: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Is inventory violating its SLOs?” through inventory: standard capacity finishes 2026-03-08 at USD 0; expedited capacity finishes 2026-03-04 at USD 750; releasing reserved capacity finishes 2026-03-03 at USD 1800 but requires approval beyond CHG-8. Recommend expedite_capacity, record its 2026-03-04 outcome and -1-day variance, and report ON_TIME honestly.",
-      "deliver": "Leave the employee-facing conclusion for “Is inventory violating its SLOs?” with the exact supported insight: record whether inventory has an active objective breach; inventory is breaching its SLO: the final finding must record an active fault; record the evidence that supports the finding; write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (expedite_capacity) in the scoped completion handoff; state the outcome date (2026-03-04) in the scoped completion handoff; state the approval reference (CHG-8) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap expedited capacity on 2026-03-04) in the scoped completion handoff. Close “Is inventory violating its SLOs?” only after the business state and readbacks are complete: close OPS-102 only once the finding is submitted, not before.",
-      "employee_outcome": "Is inventory violating its SLOs?",
-      "investigate": "Build the causal case for “Is inventory violating its SLOs?”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the PagerDuty change-event history, and the current customer-status record; finally test the competing explanation against current service measurements (inventory), actual alert firings, live Kubernetes pod state (inventory), and the employee work item. All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: record a resource exhaustion diagnosis localizing responsibility to inventory and identifying db_pool_size with cited evidence; move the employee work item to done. Preserve this additional control: an investigation must not change production state. Prove that the same outcome for “Is inventory violating its SLOs?” is deliverable through inventory, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 16 observed less 2 reserved for api-gateway leaves 14 usable and a 2-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-05 customer date.",
-      "verify": "Prove the observable result for “Is inventory violating its SLOs?” after the transition: reopen the employee work item and confirm the persisted result. After the last guarded transition for “Is inventory violating its SLOs?”, reopen the employee work item, then reopen the completion conversation so persistence and communication are both proven."
+      "change_or_record": "Establish the exact business state for “Determine whether reservation failures are a capacity incident.”: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Coordinate the linked records for “Determine whether reservation failures are a capacity incident.”: close ticket OPS-102 once reported. Keep “Determine whether reservation failures are a capacity incident.” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
+      "decide": "Choose the branch for “Determine whether reservation failures are a capacity incident.” that can legitimately produce this business state: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Determine whether reservation failures are a capacity incident.” through checkout: standard capacity finishes 2026-03-08 at USD 0; expedited capacity finishes 2026-03-04 at USD 750; releasing reserved capacity finishes 2026-03-03 at USD 1800 but requires approval beyond CHG-8. Recommend expedite_capacity, record its 2026-03-04 outcome and -1-day variance, and report ON_TIME honestly.",
+      "deliver": "Leave the employee-facing conclusion for “Determine whether reservation failures are a capacity incident.” with the exact supported insight: record whether inventory has an active objective breach; inventory is breaching its SLO: the final finding must record an active fault; record the evidence that supports the finding; write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (expedite_capacity) in the scoped completion handoff; state the outcome date (2026-03-04) in the scoped completion handoff; state the approval reference (CHG-8) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap expedited capacity on 2026-03-04) in the scoped completion handoff. Close “Determine whether reservation failures are a capacity incident.” only after the business state and readbacks are complete: close OPS-102 only once the finding is submitted, not before.",
+      "employee_outcome": "Determine whether reservation failures are a capacity incident.",
+      "investigate": "Build the causal case for “Determine whether reservation failures are a capacity incident.���: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the PagerDuty change-event history, and the current customer-status record; finally test the competing explanation against current service measurements (checkout), actual alert firings, live Kubernetes pod state (checkout), and the employee work item. All 20 exact causal facts must be present inside the 32-read investigation before they support this outcome: the service behind the symptom is inventory; identify db_pool_size as the controlling setting; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use get_service before submitting the diagnosis; the causal investigation must use list_infra before submitting the diagnosis; the causal investigation must use get_traffic_stats before submitting the diagnosis; the causal investigation must use search_logs before submitting the diagnosis; the causal investigation must use list_error_events before submitting the diagnosis; the causal investigation must use read_file before submitting the diagnosis; the causal investigation must use list_commits before submitting the diagnosis. Preserve this additional control: identify the supported fault mechanism as resource_exhaustion; an investigation must not change production state. Prove that the same outcome for “Determine whether reservation failures are a capacity incident.” is deliverable through checkout, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 16 observed less 2 reserved for inventory leaves 14 usable and a 2-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-05 customer date.",
+      "verify": "Prove the observable result for “Determine whether reservation failures are a capacity incident.” after the transition: reopen the employee work item and confirm the persisted result. After the last guarded transition for “Determine whether reservation failures are a capacity incident.”, reopen the employee work item, then reopen the completion conversation so persistence and communication are both proven."
     },
     "score_weights": {
       "analysis.capacity_plan": 9,
@@ -2455,6 +2532,6 @@
     "verifier": "verifiers/verify_dob100-008-detect-inventory.py"
   },
   "task_id": "dob100-008-detect-inventory",
-  "task_name": "Is inventory violating its SLOs?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "task_name": "Determine whether reservation failures are a capacity incident.",
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-009-rcn-checkout-error-rate.json

@@ -1542,7 +1542,7 @@
     "service": "checkout",
     "source_split": "train",
     "source_task_id": "tsk_rcn_checkout_error_rate",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2453,5 +2453,5 @@
   },
   "task_id": "dob100-009-rcn-checkout-error-rate",
   "task_name": "What is checkout's production error rate?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-010-detect-status-page-recurrence.json

@@ -1544,7 +1544,7 @@
     "service": "checkout",
     "source_split": "heldout",
     "source_task_id": "tsk_detect_status_page_recurrence",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2461,5 +2461,5 @@
   },
   "task_id": "dob100-010-detect-status-page-recurrence",
   "task_name": "Customers still cannot check out, and the status page says we fixed it.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-011-detect-storefront-healthy.json

@@ -1542,7 +1542,7 @@
     "service": "storefront-web",
     "source_split": "train",
     "source_task_id": "tsk_detect_storefront_healthy",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2451,5 +2451,5 @@
   },
   "task_id": "dob100-011-detect-storefront-healthy",
   "task_name": "Is storefront-web violating its SLOs?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-012-localize-analytics-crashloop.json

@@ -1544,7 +1544,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_localize_analytics_crashloop",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2459,5 +2459,5 @@
   },
   "task_id": "dob100-012-localize-analytics-crashloop",
   "task_name": "Alarm 9609 — the error tracker shows nothing.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-013-localize-analytics-errors.json

@@ -1546,7 +1546,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_localize_analytics_errors",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2463,5 +2463,5 @@
   },
   "task_id": "dob100-013-localize-analytics-errors",
   "task_name": "Alarm 9609 (analytics-worker errors).",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-014-localize-checkout-latency.json

@@ -1547,7 +1547,7 @@
     "service": "payments",
     "source_split": "train",
     "source_task_id": "tsk_localize_checkout_latency",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2464,5 +2464,5 @@
   },
   "task_id": "dob100-014-localize-checkout-latency",
   "task_name": "Alarm 9610 (checkout latency).",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-015-localize-gateway-latency.json

@@ -1546,7 +1546,7 @@
     "service": "api-gateway",
     "source_split": "heldout",
     "source_task_id": "tsk_localize_gateway_latency",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2463,5 +2463,5 @@
   },
   "task_id": "dob100-015-localize-gateway-latency",
   "task_name": "Alarm 9604 (api-gateway latency).",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-016-localize-media-latency.json

@@ -1546,7 +1546,7 @@
     "service": "media-service",
     "source_split": "train",
     "source_task_id": "tsk_localize_media_latency",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2463,5 +2463,5 @@
   },
   "task_id": "dob100-016-localize-media-latency",
   "task_name": "Alarm 9607 (media-service latency).",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-017-auth-v1-to-v2.json

@@ -158,21 +158,21 @@
   },
   "assets": [
     {
-      "bytes": 993,
+      "bytes": 990,
       "evidence_role": "request",
       "kind": "md",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/01-employee-request.md",
-      "sha256": "03142e2b4dbe2efe71e83babe51f43385387321a08ec5e8698d8234a6aa024d1",
+      "sha256": "2a1fc0bde33c60d4f7f40a21cee44d9c7e940ae83c4c4ae19637897bc1fbaa6c",
       "source": "employee request"
     },
     {
-      "bytes": 292,
+      "bytes": 289,
       "evidence_role": "identity",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/02-jira-work-item.csv",
-      "sha256": "7cc27e86891925fde093b48a49167dfa6467c324b39f28c424e597f428e65daf",
+      "sha256": "ebefcb27dc0ace2444bb05cca5aca4111abd9470b9e177bc435ea932a6168a9f",
       "source": "Atlassian Jira"
     },
     {
@@ -185,21 +185,21 @@
       "source": "tracker link registry"
     },
     {
-      "bytes": 193,
+      "bytes": 190,
       "evidence_role": "engineering-signal",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/04-github-issue.json",
-      "sha256": "8bf41bd7f100adab439b6b13b69664e74596639e7d09edc2939a281894e565e1",
+      "sha256": "6d6828989f8a60dc48c7be3591d61b2ea7e63abd1990fcb329db54b335b27447",
       "source": "GitHub"
     },
     {
-      "bytes": 1299,
+      "bytes": 1296,
       "evidence_role": "authority",
       "kind": "pdf",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/05-current-operating-control.pdf",
-      "sha256": "a95882a9cbb59cff4cefa2660c51091b97337b3f5267ee57a962b526edc08232",
+      "sha256": "e73ab6553768fbc417f1c6a3dd55573e2594037a2d42e6580765615c27b344e3",
       "source": "Confluence current export"
     },
     {
@@ -212,39 +212,39 @@
       "source": "Confluence history export"
     },
     {
-      "bytes": 914,
+      "bytes": 896,
       "evidence_role": "conversation",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/07-case-room-thread.json",
-      "sha256": "50869c484897271f732dcb7220ae4c63d83adf4ba666fe91aecb604969788881",
+      "sha256": "f5b741770774f540df6005fd6d4c5e54266a3242fbaff303c7666f3bea814e7d",
       "source": "Slack"
     },
     {
-      "bytes": 245,
+      "bytes": 239,
       "evidence_role": "change-history",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/08-pagerduty-change-events.csv",
-      "sha256": "623f488e5a0df114d4b38da8f08b4436f8e5e2d6ec104a3e3a39935841ae229f",
+      "sha256": "41ee536a4ec607345a0b289d3cac30dbe49c23b2e69f556822542a9d695f9d0b",
       "source": "PagerDuty"
     },
     {
-      "bytes": 1593,
+      "bytes": 1592,
       "evidence_role": "ownership",
       "kind": "xlsx",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/09-service-owner-register.xlsx",
-      "sha256": "4d38a9522ac927e725f3d935d55092cbca6cf7acc28b9dc50b6493db2335e30e",
+      "sha256": "676171248309a92a82a4403fa12e23223cfaaffc9eed985cc43c2bfd97e076b1",
       "source": "Microsoft Graph workbook"
     },
     {
-      "bytes": 1705,
+      "bytes": 1702,
       "evidence_role": "schedule",
       "kind": "xlsx",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/10-release-calendar.xlsx",
-      "sha256": "c8d39749419ac038c732d3254e17760f565ff9cf010b5097f06911015f0e983c",
+      "sha256": "f378f276cfa2068a671021fb06b97af92f44183efb29bac5063a275b7c1228b2",
       "source": "Microsoft Graph workbook"
     },
     {
@@ -284,30 +284,30 @@
       "source": "service catalog"
     },
     {
-      "bytes": 131,
+      "bytes": 125,
       "evidence_role": "live-signal",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/15-slo-export.csv",
-      "sha256": "f064e0d45010f16a4d31e80b460afad0be8b27423cc4af561aef2f5edce8412a",
+      "sha256": "a36f68b2a28241666575e73e6d0a93e65de6f224b4d39ab25fa1546a09992ab8",
       "source": "SLO platform"
     },
     {
-      "bytes": 152,
+      "bytes": 147,
       "evidence_role": "live-signal",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/16-metrics-export.csv",
-      "sha256": "db605f324f228308279673c0b37176c41ec8cc3e1f79876ff36dfd4191b268cb",
+      "sha256": "8cbd546cc92853941daab9ce5360ab3f0a752b1e5d9332fc83a9cbe48c05948d",
       "source": "Prometheus"
     },
     {
-      "bytes": 68,
+      "bytes": 486,
       "evidence_role": "live-signal",
       "kind": "log",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/17-observability-log-slice.log",
-      "sha256": "df7af03f2ae02989de8f7e97b94ea77194a1876439e26190569efb591e0124bb",
+      "sha256": "4202624f5dda66f04de958875b57fca942be0e2e048d8f86f26a90c2525e1f9b",
       "source": "log platform"
     },
     {
@@ -320,12 +320,12 @@
       "source": "Sentry"
     },
     {
-      "bytes": 24,
+      "bytes": 261,
       "evidence_role": "runtime-state",
       "kind": "yaml",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/19-kubernetes-pods.yaml",
-      "sha256": "64dc710a82c3a80f26eeea167bc29f5c782e3ec5f12abf210167e94b0c0b60da",
+      "sha256": "7a5e311647d46ce0ab1c4cbca77f3e500eb522973fb120c511214b89f797706f",
       "source": "Kubernetes"
     },
     {
@@ -338,30 +338,30 @@
       "source": "Kubernetes"
     },
     {
-      "bytes": 439,
+      "bytes": 816,
       "evidence_role": "deployment-state",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/21-deployment-history.json",
-      "sha256": "5ce229175b842c0438afc6cbe3c0ac4bc1fb9505f3bb0321fa35fc5429545691",
+      "sha256": "2a9e0797d3cdf796d22765b77f49b9292d600819b9e73b454edca9e01eda8ce5",
       "source": "deployment platform"
     },
     {
-      "bytes": 57,
+      "bytes": 101,
       "evidence_role": "build-state",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/22-ci-runs.csv",
-      "sha256": "0d340952b28658d09db92495984f15abaf8455058ea75efd84405553816108cc",
+      "sha256": "1620f2a484197863860cba334628b56197349adb4b880a4ef639d72e43fc6fee",
       "source": "CI platform"
     },
     {
-      "bytes": 50,
+      "bytes": 316,
       "evidence_role": "change-state",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/23-pull-request-context.json",
-      "sha256": "cac7331669624617fa927d4970fc7f4efd287a821a938d2ce319c5dbf13fa188",
+      "sha256": "5795e6f30ad1d59c5f87e5abaf53e745f1de202487764344e0d6331594587172",
       "source": "GitHub"
     },
     {
@@ -401,52 +401,52 @@
       "source": "evidence custodian"
     },
     {
-      "bytes": 2681,
+      "bytes": 2672,
       "evidence_role": "capacity requirement",
       "kind": "pdf",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/28-change-readiness-standard.pdf",
-      "sha256": "c1a72c625dded562785e70d0aa5cc270022909f0267a13ee07b40372155fb1eb",
+      "sha256": "54f0cbd185a828b07add5a183f86d873fa35aa1b6f73c16b75a4df743a2ea62b",
       "source": "Confluence current export"
     },
     {
-      "bytes": 325,
+      "bytes": 319,
       "evidence_role": "vendor lead time and cost",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/29-vendor-capacity-order.csv",
-      "sha256": "d7d5b7e844cc0500872264e6c185f75be17290986c9e9158b42a3a24b6870000",
+      "sha256": "84b226ddb7a5a2d9d62604b7b0f28e0fc42f47b6515f29ea34982318f27a6dda",
       "source": "Atlassian Jira vendor project"
     },
     {
-      "bytes": 411,
+      "bytes": 405,
       "evidence_role": "approval scope",
       "kind": "csv",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/30-change-approval-record.csv",
-      "sha256": "725d75c562a6bc5801e2a74b0b1b30f2ef367f38f7784e8a97465504f3887b34",
+      "sha256": "fb76b3e9ecc92faf013bd002c7ef96ee6df33dd5684dcdfeb5a577d31210aaab",
       "source": "Atlassian Jira change advisory"
     },
     {
-      "bytes": 422,
+      "bytes": 421,
       "evidence_role": "capacity exclusion",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/31-capacity-reservation-register.json",
-      "sha256": "fe1a8d162f02becef530204893ca8338f9ea506ad6d153f1b556525c9c6ca8ee",
+      "sha256": "8ae1f9c5f7c55dc670af8b918b2f725cae0b38baa7211a6f0eb3ecea33968b1e",
       "source": "Linear"
     },
     {
-      "bytes": 266,
+      "bytes": 263,
       "evidence_role": "independent business need",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/32-customer-cutover-notice.json",
-      "sha256": "b077facbacb36e5748eb21d436dab450debda8ca010430d27c1a5f76faf42aaf",
+      "sha256": "0e96ded680daecd9f0b562527f0e9279bdeefc13d7aabe6aa5bb3ad170ae190c",
       "source": "public status page"
     },
     {
-      "bytes": 771,
+      "bytes": 768,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -455,7 +455,7 @@
       "query_scope": {
         "key": "DOB-017"
       },
-      "sha256": "6315c95fb510006c4e5862cf2920f7faeed277cac27bb38b383a436079f1d7a9",
+      "sha256": "257e7f3c777a79713e9e9b719d8e0332952618656984c92fccb1b078b4ac12f5",
       "source": "the authoritative Jira work item"
     },
     {
@@ -472,21 +472,21 @@
       "source": "the cross-tracker link registry"
     },
     {
-      "bytes": 548,
+      "bytes": 542,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the linked GitHub issue population",
       "path": "task_files/dob100-017-auth-v1-to-v2/material/03-the-linked-github-issue-population.json",
       "query_scope": {
-        "repo": "novacart/storefront-web",
+        "repo": "novacart/api-gateway",
         "state": "open"
       },
-      "sha256": "55b51f43ca2d8c7c27b93f1009bf1a78566429d22b21c119639c6a9ba5ea41e9",
+      "sha256": "ebc94ab8a0013443889801669c5d00e85bfc5a4619705dd81836ab1138f3601c",
       "source": "the linked GitHub issue population"
     },
     {
-      "bytes": 791,
+      "bytes": 788,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -496,11 +496,11 @@
         "query": "DOB-017",
         "space": "OPS"
       },
-      "sha256": "16e3b8ac3f8ca4b550ac25d1c20311e318378a4738093e2f0d9119c1c3043eeb",
+      "sha256": "1d4923211d124b199647ae84ed58f5b11aa27cf1a184f8bf9e9233f1f4fb9c1a",
       "source": "the operating-control index"
     },
     {
-      "bytes": 1092,
+      "bytes": 1089,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -509,7 +509,7 @@
       "query_scope": {
         "page_id": 10017
       },
-      "sha256": "cfccc35214cfd308fe38d983e4e9c90ab1a744ef3ea06aadddcfbf66c832963a",
+      "sha256": "fa502a41abb1aaa4e101112b69428b3693c875ec2f160c176cb1716106a0fc80",
       "source": "the exact control revision"
     },
     {
@@ -526,17 +526,17 @@
       "source": "the exact control revision"
     },
     {
-      "bytes": 1272,
+      "bytes": 1251,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the case-room conversation",
       "path": "task_files/dob100-017-auth-v1-to-v2/material/07-the-case-room-conversation.json",
       "query_scope": {
-        "channel": "case-017-storefront-web",
+        "channel": "case-017-api-gateway",
         "limit": 50
       },
-      "sha256": "3d661e415104da8a1f108fcb884585ac1cf4f579697e6f43611c67e66cb939da",
+      "sha256": "db920609f58d529b376a0a66466a605b455742575ac22f600347986b0e1d5a98",
       "source": "the case-room conversation"
     },
     {
@@ -551,7 +551,7 @@
       "source": "the operative approval policy"
     },
     {
-      "bytes": 709,
+      "bytes": 703,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -561,7 +561,7 @@
         "pd_service_id": "PD-DOB-017",
         "since_day": 330
       },
-      "sha256": "d21f0bc891227bea1402a8cbf245939db9cb6544a851ae676bb9d3262e7de7c0",
+      "sha256": "2c6a43fbaf1a9fc55f920f265f8b17e97524b7a20647c4213ff30bcb7de8985c",
       "source": "the PagerDuty change-event history"
     },
     {
@@ -617,7 +617,7 @@
       "source": "the served API surface"
     },
     {
-      "bytes": 2317,
+      "bytes": 2308,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -626,11 +626,11 @@
       "query_scope": {
         "page_id": 14017
       },
-      "sha256": "bbae69508c6efd5cee7a94562610a1d202ad639f9b7af519eea1e172060296a7",
+      "sha256": "fa93216b78135bf94cdeae518e6421286e65cde7c128af5cc4b20013746762b8",
       "source": "the exact control revision"
     },
     {
-      "bytes": 726,
+      "bytes": 720,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -639,11 +639,11 @@
       "query_scope": {
         "key": "VEND-17"
       },
-      "sha256": "e431df049cce2c97e52efffd119a88f1b62d3c43a4355f4f8c3138a8a54ba28f",
+      "sha256": "85e87b41c75324dae7a1e8f92450991d5ed665edd5bb1d63d4593a6cbdfabea3",
       "source": "the authoritative Jira work item"
     },
     {
-      "bytes": 813,
+      "bytes": 807,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -652,24 +652,24 @@
       "query_scope": {
         "key": "CHG-17"
       },
-      "sha256": "ea8957aa32a2dbb2b461246e24c1509dd2c4babd906d06fef08cae1ea40efff7",
+      "sha256": "aabaa7f41b54995b63b3e7e81af3a8aebf16a0536469c70692ae5e786cd212ef",
       "source": "the authoritative Jira work item"
     },
     {
-      "bytes": 667,
+      "bytes": 663,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the linked planning tracker",
       "path": "task_files/dob100-017-auth-v1-to-v2/material/17-the-linked-planning-tracker.json",
       "query_scope": {
-        "team": "team-storefront-web"
+        "team": "team-api-gateway"
       },
-      "sha256": "f2472d7e040be397f42635a067739c6ce05234cc856207be1174fa08388d6ac1",
+      "sha256": "42ce82c50c8e7e4c735a1e51f4830893beb6c451cdd748215cb59d33077e6185",
       "source": "the linked planning tracker"
     },
     {
-      "bytes": 1089,
+      "bytes": 1086,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
@@ -678,18 +678,18 @@
       "query_scope": {
         "since_day": 330
       },
-      "sha256": "f77ec52bd3bd649200d058f63d3b8b94c2d4920c7b5c0e282ce66bcd21b6b3b4",
+      "sha256": "6f325cf5a4180658fed63942897e9f6adce30dfee6b8a718ce00e61a27cdf1a2",
       "source": "customer-status history"
     },
     {
-      "bytes": 1549,
+      "bytes": 1540,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current owner register",
       "path": "task_files/dob100-017-auth-v1-to-v2/material/19-the-current-owner-register.json",
       "query_scope": {},
-      "sha256": "38ab08c0e2bbef1787c91cd6a4249d99ecdffe45ce07213e6bf82bf971eed48a",
+      "sha256": "64b660c79799471f102983fe10f60dc6c69124ba743c80860d5a71671755ef0d",
       "source": "the current owner register"
     },
     {
@@ -704,12 +704,12 @@
       "source": "the PagerDuty service catalog"
     },
     {
-      "bytes": 18322,
+      "bytes": 18317,
       "evidence_role": "manifest",
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-017-auth-v1-to-v2/51-agent-visible-asset-manifest.json",
-      "sha256": "10b31c0b161ced2ae8a376fc9f61180cf1169b2e17ba81486849c04094910c80",
+      "sha256": "c24e7cd236f1ee8bc88fd7bda3473205103afda121df7984107864021dc03f91",
       "source": "release builder"
     }
   ],
@@ -796,7 +796,7 @@
       },
       {
         "check_id": "correctness.v5_answer_required_replicas",
-        "description": "Derived 4 per zone x 4 zones = 16 replicas required before the storefront-web cutover.",
+        "description": "Derived 4 per zone x 4 zones = 16 replicas required before the api-gateway cutover.",
         "field": "required_replicas",
         "id": "derive_plan_requirement",
         "milestone_id": "analysis.capacity_plan",
@@ -804,7 +804,7 @@
       },
       {
         "check_id": "correctness.v5_answer_observed_replicas",
-        "description": "Read 17 replicas in the storefront-web production pool from the PagerDuty scale record.",
+        "description": "Read 17 replicas in the api-gateway production pool from the PagerDuty scale record.",
         "field": "observed_replicas",
         "id": "read_gross_coverage",
         "milestone_id": "analysis.capacity_plan",
@@ -812,7 +812,7 @@
       },
       {
         "check_id": "correctness.v5_answer_reserved_replicas",
-        "description": "Excluded 4 replicas reserved for the api-gateway freeze in Linear CAP-17.",
+        "description": "Excluded 4 replicas reserved for the analytics-worker freeze in Linear CAP-17.",
         "field": "reserved_replicas",
         "id": "remove_ineligible_coverage",
         "milestone_id": "analysis.capacity_plan",
@@ -868,7 +868,7 @@
       },
       {
         "check_id": "correctness.v5_answer_next_change_window",
-        "description": "Read the storefront-web change calendar (2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11) from the current operating control and identified 2026-03-05 as the next window.",
+        "description": "Read the api-gateway change calendar (2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11) from the current operating control and identified 2026-03-05 as the next window.",
         "field": "next_change_window",
         "id": "identify_safe_window",
         "milestone_id": "analysis.capacity_plan",
@@ -959,12 +959,12 @@
     "facts": [
       {
         "id": "authoritative_identity",
-        "rubric": "Located DOB-017 for storefront-web through immutable Jira and GitHub identities and preserved OPS-CONTROL-2026.03 as the effective control.",
+        "rubric": "Located DOB-017 for api-gateway through immutable Jira and GitHub identities and preserved OPS-CONTROL-2026.03 as the effective control.",
         "sources": [
           "jira",
           "github"
         ],
-        "statement": "DOB-017 resolves to Jira DOB-017 and GitHub issue #9017 for storefront-web; the effective control is OPS-CONTROL-2026.03."
+        "statement": "DOB-017 resolves to Jira DOB-017 and GitHub issue #9017 for api-gateway; the effective control is OPS-CONTROL-2026.03."
       },
       {
         "id": "effective_requirement",
@@ -982,7 +982,7 @@
           "pagerduty",
           "linear"
         ],
-        "statement": "The pool holds 17 replicas; 4 are reserved for the api-gateway freeze, leaving 13 usable and a gap of 3."
+        "statement": "The pool holds 17 replicas; 4 are reserved for the analytics-worker freeze, leaving 13 usable and a gap of 3."
       },
       {
         "id": "conditional_external_recovery",
@@ -994,11 +994,11 @@
       },
       {
         "id": "finite_capacity",
-        "rubric": "Applied the published storefront-web change calendar to derive every plan's completion without using excluded or unapproved scope.",
+        "rubric": "Applied the published api-gateway change calendar to derive every plan's completion without using excluded or unapproved scope.",
         "sources": [
           "confluence"
         ],
-        "statement": "Change windows for storefront-web are 2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11; work outside a window needs incident-commander approval."
+        "statement": "Change windows for api-gateway are 2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11; work outside a window needs incident-commander approval."
       },
       {
         "id": "approval_scope",
@@ -1043,7 +1043,7 @@
       {
         "approval": "ADDITIONAL_APPROVAL_REQUIRED",
         "completion": "2026-03-03",
-        "consequence": "Releasing the 4 replicas reserved for the api-gateway freeze would cover the 3-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-17, and adds the USD 1600 re-provisioning charge.",
+        "consequence": "Releasing the 4 replicas reserved for the analytics-worker freeze would cover the 3-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-17, and adds the USD 1600 re-provisioning charge.",
         "control_status": "SEPARATE_APPROVAL_OR_POLICY_EXCEPTION_REQUIRED",
         "id": "release_reserved_capacity",
         "incremental_cost": 1600,
@@ -1057,7 +1057,7 @@
     "selected_completion": "2026-03-07",
     "selected_option": "standard_capacity_plan",
     "source_document": "DOB-017 change-readiness standard, CloudCap order VEND-17, change approval CHG-17",
-    "subject": "storefront-web customer cutover readiness for DOB-017"
+    "subject": "api-gateway customer cutover readiness for DOB-017"
   },
   "expected": {
     "answer": {
@@ -1439,11 +1439,11 @@
     ],
     "reasoning_contract": {
       "change_or_record": "Establish the exact business state for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Coordinate the linked records for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: a merged pull request must be linked to ENG-2402; ticket ENG-2402 must be closed (status done); the pull request must carry a description explaining the change. Keep “Migrate /v1/auth traffic to /v2/auth and retire v1.” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
-      "decide": "Choose the branch for “Migrate /v1/auth traffic to /v2/auth and retire v1.” that can legitimately produce this business state: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Migrate /v1/auth traffic to /v2/auth and retire v1.” through storefront-web: standard capacity finishes 2026-03-07 at USD 0; expedited capacity finishes 2026-03-05 at USD 1050; releasing reserved capacity finishes 2026-03-03 at USD 1600 but requires approval beyond CHG-17. Recommend standard_capacity_plan, record its 2026-03-07 outcome and +0-day variance, and report ON_TIME honestly.",
+      "decide": "Choose the branch for “Migrate /v1/auth traffic to /v2/auth and retire v1.” that can legitimately produce this business state: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Migrate /v1/auth traffic to /v2/auth and retire v1.” through api-gateway: standard capacity finishes 2026-03-07 at USD 0; expedited capacity finishes 2026-03-05 at USD 1050; releasing reserved capacity finishes 2026-03-03 at USD 1600 but requires approval beyond CHG-17. Recommend standard_capacity_plan, record its 2026-03-07 outcome and +0-day variance, and report ON_TIME honestly.",
       "deliver": "Leave the employee-facing conclusion for “Migrate /v1/auth traffic to /v2/auth and retire v1.” with the exact supported insight: write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (standard_capacity_plan) in the scoped completion handoff; state the outcome date (2026-03-07) in the scoped completion handoff; state the approval reference (CHG-17) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap standard capacity on 2026-03-07) in the scoped completion handoff. Close “Migrate /v1/auth traffic to /v2/auth and retire v1.” only after the business state and readbacks are complete: close ENG-2402 only once the work is actually done, not before.",
       "employee_outcome": "Migrate /v1/auth traffic to /v2/auth and retire v1.",
-      "investigate": "Build the causal case for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the operative approval policy, and the PagerDuty change-event history; finally test the competing explanation against the exact operating document, the current operating standard (for api), and the served API surface (api-gateway). All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Prove that the same outcome for “Migrate /v1/auth traffic to /v2/auth and retire v1.” is deliverable through storefront-web, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 17 observed less 4 reserved for api-gateway leaves 13 usable and a 3-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-07 customer date.",
-      "verify": "Prove the observable result for “Migrate /v1/auth traffic to /v2/auth and retire v1.” after the transition: the retirement pull request must have passed all four CI stages including regression; no deployment may trip a new alarm; reopen current code-review state (storefront-web), the deployment ledger (storefront-web), current code-review state (api-gateway), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item and confirm the persisted result. After the last guarded transition for “Migrate /v1/auth traffic to /v2/auth and retire v1.”, reopen current code-review state (storefront-web), the deployment ledger (storefront-web), current code-review state (api-gateway), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item, then reopen the completion conversation so persistence and communication are both proven."
+      "investigate": "Build the causal case for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the operative approval policy, and the PagerDuty change-event history; finally test the competing explanation against the exact operating document, the current operating standard (for api), and the served API surface (api-gateway). All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Prove that the same outcome for “Migrate /v1/auth traffic to /v2/auth and retire v1.” is deliverable through api-gateway, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 17 observed less 4 reserved for analytics-worker leaves 13 usable and a 3-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-07 customer date.",
+      "verify": "Prove the observable result for “Migrate /v1/auth traffic to /v2/auth and retire v1.” after the transition: the retirement pull request must have passed all four CI stages including regression; no deployment may trip a new alarm; reopen current code-review state (storefront-web), current code-review state (api-gateway), the deployment ledger (storefront-web), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item and confirm the persisted result. After the last guarded transition for “Migrate /v1/auth traffic to /v2/auth and retire v1.”, reopen current code-review state (storefront-web), current code-review state (api-gateway), the deployment ledger (storefront-web), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item, then reopen the completion conversation so persistence and communication are both proven."
     },
     "reference_assets": [
       "task_files/dob100-017-auth-v1-to-v2/01-employee-request.md",
@@ -1564,15 +1564,15 @@
       "execute_run_ci",
       "execute_shift_endpoint_traffic",
       "execute_update_ticket",
-      "plan_storefront_web_cutover_capacity_standard_capacity_plan",
+      "plan_api_gateway_cutover_capacity_standard_capacity_plan",
       "reconcile_auth_v1_to_v2_post_change_state",
       "handoff_source_backed_result_to_owner",
       "reopen_persisted_state_and_conversation"
     ],
-    "service": "storefront-web",
+    "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_auth_v1_to_v2",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -1591,33 +1591,33 @@
       "milestone_id": "verification.outcome"
     },
     {
-      "after_tool": "deploy_service",
+      "after_tool": "merge_pull_request",
       "any_of": [
         {
           "arguments": {
-            "limit": 20,
-            "service": "storefront-web"
+            "service": "api-gateway"
           },
-          "tool": "list_deployments"
+          "tool": "list_pull_requests"
         }
       ],
       "check_id": "deployment.v4_state_readbacks_complete",
-      "description": "Reopened list_deployments after deploy_service for DOB-017 and confirmed persisted provider state, not merely the write acknowledgement.",
+      "description": "Reopened list_pull_requests after merge_pull_request for DOB-017 and confirmed persisted provider state, not merely the write acknowledgement.",
       "id": "readback_02",
       "milestone_id": "verification.outcome"
     },
     {
-      "after_tool": "open_pull_request",
+      "after_tool": "deploy_service",
       "any_of": [
         {
           "arguments": {
-            "service": "api-gateway"
+            "limit": 20,
+            "service": "storefront-web"
           },
-          "tool": "list_pull_requests"
+          "tool": "list_deployments"
         }
       ],
       "check_id": "deployment.v4_state_readbacks_complete",
-      "description": "Reopened list_pull_requests after open_pull_request for DOB-017 and confirmed persisted provider state, not merely the write acknowledgement.",
+      "description": "Reopened list_deployments after deploy_service for DOB-017 and confirmed persisted provider state, not merely the write acknowledgement.",
       "id": "readback_03",
       "milestone_id": "verification.outcome"
     },
@@ -1668,7 +1668,7 @@
       "milestone_id": "verification.outcome"
     }
   ],
-  "prompt": "Migrate /v1/auth traffic to /v2/auth and retire v1. Consumers still span the old and replacement contract, so establish actual usage, compatibility, and rollback conditions before completing the traffic transition. For api-gateway → storefront-web capability chain, the affected business boundary includes the upstream-to-downstream dependency direction, the contract at each service boundary, ownership, recoverability, and end-to-end health. The change boundary covers tokens, identity sessions, compatibility headers, and authentication consumers. Choose the supported rollout path from the evidence available today, stop if its control conditions are not met, and document what you observed afterward. This production change and the 2026-03-07 cutover for storefront-web are one release decision. Give management a decision, not a copied milestone: the supported completion, the binding constraint, the price of acceleration, and the consequence of the option that needs more authority.",
+  "prompt": "Migrate /v1/auth traffic to /v2/auth and retire v1. Consumers still span the old and replacement contract, so establish actual usage, compatibility, and rollback conditions before completing the traffic transition. For api-gateway → storefront-web capability chain, the affected business boundary includes the upstream-to-downstream dependency direction, the contract at each service boundary, ownership, recoverability, and end-to-end health. The change boundary covers tokens, identity sessions, compatibility headers, and authentication consumers. Choose the supported rollout path from the evidence available today, stop if its control conditions are not met, and document what you observed afterward. This production change and the 2026-03-07 cutover for api-gateway are one release decision. Give management a decision, not a copied milestone: the supported completion, the binding constraint, the price of acceleration, and the consequence of the option that needs more authority.",
   "required_investigations": [
     {
       "any_of": [
@@ -1706,7 +1706,7 @@
       "any_of": [
         {
           "arguments": {
-            "repo": "novacart/storefront-web",
+            "repo": "novacart/api-gateway",
             "state": "open"
           },
           "tool": "github_list_issues"
@@ -1714,7 +1714,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_case_identity_resolved",
-      "description": "Located GitHub issue #9017 in novacart/storefront-web by immutable number.",
+      "description": "Located GitHub issue #9017 in novacart/api-gateway by immutable number.",
       "group": "identity",
       "id": "investigation_03",
       "milestone_id": "investigation.scope"
@@ -1747,7 +1747,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_authority_reconciled",
-      "description": "Applied OPS-CONTROL-2026.03 and its storefront-web change windows: 2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11.",
+      "description": "Applied OPS-CONTROL-2026.03 and its api-gateway change windows: 2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11.",
       "group": "authority",
       "id": "investigation_05",
       "milestone_id": "investigation.authority"
@@ -1772,7 +1772,7 @@
       "any_of": [
         {
           "arguments": {
-            "channel": "case-017-storefront-web",
+            "channel": "case-017-api-gateway",
             "limit": 50
           },
           "tool": "list_messages"
@@ -1780,7 +1780,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Separated the case-room business request from formal operational authority for storefront-web.",
+      "description": "Separated the case-room business request from formal operational authority for api-gateway.",
       "group": "ownership_and_conversation",
       "id": "investigation_07",
       "milestone_id": "analysis.causal_reasoning"
@@ -1794,7 +1794,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Correlated the live storefront-web list_approval_policy record that controls the api_migration decision.",
+      "description": "Correlated the live api-gateway list_approval_policy record that controls the api_migration decision.",
       "group": "ownership_and_conversation",
       "id": "investigation_08",
       "milestone_id": "analysis.causal_reasoning"
@@ -1811,7 +1811,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Read the live storefront-web pool record: 17 replicas across 4 zones.",
+      "description": "Read the live api-gateway pool record: 17 replicas across 4 zones.",
       "group": "ownership_and_conversation",
       "id": "investigation_09",
       "milestone_id": "analysis.causal_reasoning"
@@ -1827,7 +1827,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live storefront-web get_document record that controls the api_migration decision.",
+      "description": "Correlated the live api-gateway get_document record that controls the api_migration decision.",
       "group": "live_state",
       "id": "investigation_10",
       "milestone_id": "investigation.live_state"
@@ -1843,7 +1843,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live storefront-web search_docs record that controls the api_migration decision.",
+      "description": "Correlated the live api-gateway search_docs record that controls the api_migration decision.",
       "group": "live_state",
       "id": "investigation_11",
       "milestone_id": "investigation.live_state"
@@ -1859,7 +1859,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live storefront-web get_document record that controls the api_migration decision.",
+      "description": "Correlated the live api-gateway get_document record that controls the api_migration decision.",
       "group": "live_state",
       "id": "investigation_12",
       "milestone_id": "investigation.live_state"
@@ -1875,7 +1875,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_live_state_correlated",
-      "description": "Correlated the live storefront-web list_api_endpoints record that controls the api_migration decision.",
+      "description": "Correlated the live api-gateway list_api_endpoints record that controls the api_migration decision.",
       "group": "live_state",
       "id": "investigation_13",
       "milestone_id": "investigation.live_state"
@@ -1891,7 +1891,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v5_capacity_evidence_complete",
-      "description": "Established the storefront-web requirement of 4 healthy replicas in each production zone.",
+      "description": "Established the api-gateway requirement of 4 healthy replicas in each production zone.",
       "group": "capacity_plan",
       "id": "investigation_14",
       "milestone_id": "analysis.capacity_plan"
@@ -1932,14 +1932,14 @@
       "any_of": [
         {
           "arguments": {
-            "team": "team-storefront-web"
+            "team": "team-api-gateway"
           },
           "tool": "linear_list_issues"
         }
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v5_capacity_evidence_complete",
-      "description": "Excluded 4 replicas reserved for the api-gateway freeze.",
+      "description": "Excluded 4 replicas reserved for the analytics-worker freeze.",
       "group": "capacity_plan",
       "id": "investigation_17",
       "milestone_id": "analysis.capacity_plan"
@@ -1969,7 +1969,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Confirmed the accountable storefront-web owner and scoped case channel.",
+      "description": "Confirmed the accountable api-gateway owner and scoped case channel.",
       "group": "corroborating_context",
       "id": "investigation_19",
       "milestone_id": "analysis.causal_reasoning"
@@ -1983,7 +1983,7 @@
       ],
       "before_primary_mutation": true,
       "check_id": "correctness.v4_material_evidence_complete",
-      "description": "Correlated the live storefront-web pd_list_services record that controls the api_migration decision.",
+      "description": "Correlated the live api-gateway pd_list_services record that controls the api_migration decision.",
       "group": "corroborating_context",
       "id": "investigation_20",
       "milestone_id": "analysis.causal_reasoning"
@@ -2040,7 +2040,7 @@
       {
         "atomic_checks": [
           {
-            "description": "correlate the task-specific storefront-web provider state instead of relying on files or tracker text alone",
+            "description": "correlate the task-specific api-gateway provider state instead of relying on files or tracker text alone",
             "dimension": "correctness",
             "id": "correctness.v4_live_state_correlated",
             "name": "v4_live_state_correlated"
@@ -2086,19 +2086,19 @@
             "name": "v5_answer_production_zones"
           },
           {
-            "description": "Derived 4 per zone x 4 zones = 16 replicas required before the storefront-web cutover.",
+            "description": "Derived 4 per zone x 4 zones = 16 replicas required before the api-gateway cutover.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_required_replicas",
             "name": "v5_answer_required_replicas"
           },
           {
-            "description": "Read 17 replicas in the storefront-web production pool from the PagerDuty scale record.",
+            "description": "Read 17 replicas in the api-gateway production pool from the PagerDuty scale record.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_observed_replicas",
             "name": "v5_answer_observed_replicas"
           },
           {
-            "description": "Excluded 4 replicas reserved for the api-gateway freeze in Linear CAP-17.",
+            "description": "Excluded 4 replicas reserved for the analytics-worker freeze in Linear CAP-17.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_reserved_replicas",
             "name": "v5_answer_reserved_replicas"
@@ -2140,7 +2140,7 @@
             "name": "v5_answer_capacity_request_replicas"
           },
           {
-            "description": "Read the storefront-web change calendar (2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11) from the current operating control and identified 2026-03-05 as the next window.",
+            "description": "Read the api-gateway change calendar (2026-03-05, 2026-03-07, 2026-03-09, 2026-03-11) from the current operating control and identified 2026-03-05 as the next window.",
             "dimension": "correctness",
             "id": "correctness.v5_answer_next_change_window",
             "name": "v5_answer_next_change_window"
@@ -2153,7 +2153,7 @@
           }
         ],
         "category": "analysis",
-        "description": "Prove that the same outcome for “Migrate /v1/auth traffic to /v2/auth and retire v1.” is deliverable through storefront-web, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 17 observed less 4 reserved for api-gateway leaves 13 usable and a 3-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-07 customer date.",
+        "description": "Prove that the same outcome for “Migrate /v1/auth traffic to /v2/auth and retire v1.” is deliverable through api-gateway, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 17 observed less 4 reserved for analytics-worker leaves 13 usable and a 3-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-07 customer date.",
         "id": "analysis.capacity_plan",
         "weight": 9
       },
@@ -2247,7 +2247,7 @@
           }
         ],
         "category": "decision",
-        "description": "Compare three concrete, linked readiness options for “Migrate /v1/auth traffic to /v2/auth and retire v1.” through storefront-web: standard capacity finishes 2026-03-07 at USD 0; expedited capacity finishes 2026-03-05 at USD 1050; releasing reserved capacity finishes 2026-03-03 at USD 1600 but requires approval beyond CHG-17. Recommend standard_capacity_plan, record its 2026-03-07 outcome and +0-day variance, and report ON_TIME honestly.",
+        "description": "Compare three concrete, linked readiness options for “Migrate /v1/auth traffic to /v2/auth and retire v1.” through api-gateway: standard capacity finishes 2026-03-07 at USD 0; expedited capacity finishes 2026-03-05 at USD 1050; releasing reserved capacity finishes 2026-03-03 at USD 1600 but requires approval beyond CHG-17. Recommend standard_capacity_plan, record its 2026-03-07 outcome and +0-day variance, and report ON_TIME honestly.",
         "id": "decision.options",
         "weight": 8
       },
@@ -2343,7 +2343,7 @@
           }
         ],
         "category": "verification",
-        "description": "Prove the observable result for “Migrate /v1/auth traffic to /v2/auth and retire v1.” after the transition: the retirement pull request must have passed all four CI stages including regression; no deployment may trip a new alarm; reopen current code-review state (storefront-web), the deployment ledger (storefront-web), current code-review state (api-gateway), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item and confirm the persisted result.",
+        "description": "Prove the observable result for “Migrate /v1/auth traffic to /v2/auth and retire v1.” after the transition: the retirement pull request must have passed all four CI stages including regression; no deployment may trip a new alarm; reopen current code-review state (storefront-web), current code-review state (api-gateway), the deployment ledger (storefront-web), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item and confirm the persisted result.",
         "id": "verification.outcome",
         "weight": 7
       },
@@ -2363,7 +2363,7 @@
           }
         ],
         "category": "verification",
-        "description": "After the last guarded transition for “Migrate /v1/auth traffic to /v2/auth and retire v1.”, reopen current code-review state (storefront-web), the deployment ledger (storefront-web), current code-review state (api-gateway), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item, then reopen the completion conversation so persistence and communication are both proven.",
+        "description": "After the last guarded transition for “Migrate /v1/auth traffic to /v2/auth and retire v1.”, reopen current code-review state (storefront-web), current code-review state (api-gateway), the deployment ledger (storefront-web), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item, then reopen the completion conversation so persistence and communication are both proven.",
         "id": "verification.readback",
         "weight": 6
       },
@@ -2586,12 +2586,12 @@
       {
         "approval": "ADDITIONAL_APPROVAL_REQUIRED",
         "completion": "2026-03-03",
-        "consequence": "Releasing the 4 replicas reserved for the api-gateway freeze would cover the 3-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-17, and adds the USD 1600 re-provisioning charge.",
+        "consequence": "Releasing the 4 replicas reserved for the analytics-worker freeze would cover the 3-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-17, and adds the USD 1600 re-provisioning charge.",
         "control_status": "SEPARATE_APPROVAL_OR_POLICY_EXCEPTION_REQUIRED",
         "id": "release_reserved_capacity",
         "incremental_cost": 1600,
         "label": "release_reserved_capacity: outcome 2026-03-03, incremental cost USD 1600, SEPARATE_APPROVAL_OR_POLICY_EXCEPTION_REQUIRED",
-        "reason": "Releasing the 4 replicas reserved for the api-gateway freeze covers the gap today but needs approval beyond CHG-17. Releasing the 4 replicas reserved for the api-gateway freeze would cover the 3-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-17, and adds the USD 1600 re-provisioning charge.",
+        "reason": "Releasing the 4 replicas reserved for the analytics-worker freeze covers the gap today but needs approval beyond CHG-17. Releasing the 4 replicas reserved for the analytics-worker freeze would cover the 3-replica gap today, but it breaks a reservation another team depends on, needs incident-commander approval beyond CHG-17, and adds the USD 1600 re-provisioning charge.",
         "recommended": false,
         "selected": false
       }
@@ -2601,11 +2601,11 @@
     "pass_rule": "all 16 semantic milestones hold over causal tool evidence, the graded capacity-plan decision record, final world state, readback, and containment",
     "reasoning_contract": {
       "change_or_record": "Establish the exact business state for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Coordinate the linked records for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: a merged pull request must be linked to ENG-2402; ticket ENG-2402 must be closed (status done); the pull request must carry a description explaining the change. Keep “Migrate /v1/auth traffic to /v2/auth and retire v1.” contained to its supported records and service boundary: fabricate no records or evidence; preserve every frozen out-of-scope record; introduce no hardcoded credentials.",
-      "decide": "Choose the branch for “Migrate /v1/auth traffic to /v2/auth and retire v1.” that can legitimately produce this business state: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Migrate /v1/auth traffic to /v2/auth and retire v1.” through storefront-web: standard capacity finishes 2026-03-07 at USD 0; expedited capacity finishes 2026-03-05 at USD 1050; releasing reserved capacity finishes 2026-03-03 at USD 1600 but requires approval beyond CHG-17. Recommend standard_capacity_plan, record its 2026-03-07 outcome and +0-day variance, and report ON_TIME honestly.",
+      "decide": "Choose the branch for “Migrate /v1/auth traffic to /v2/auth and retire v1.” that can legitimately produce this business state: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Reject a stale-record shortcut, an unsupported hold, and any broader workaround. Compare three concrete, linked readiness options for “Migrate /v1/auth traffic to /v2/auth and retire v1.” through api-gateway: standard capacity finishes 2026-03-07 at USD 0; expedited capacity finishes 2026-03-05 at USD 1050; releasing reserved capacity finishes 2026-03-03 at USD 1600 but requires approval beyond CHG-17. Recommend standard_capacity_plan, record its 2026-03-07 outcome and +0-day variance, and report ON_TIME honestly.",
       "deliver": "Leave the employee-facing conclusion for “Migrate /v1/auth traffic to /v2/auth and retire v1.” with the exact supported insight: write a natural scoped completion note, not a keyword list or serialized benchmark object; state the selected option (standard_capacity_plan) in the scoped completion handoff; state the outcome date (2026-03-07) in the scoped completion handoff; state the approval reference (CHG-17) in the scoped completion handoff; state the timing status (ON_TIME) in the scoped completion handoff; state the binding constraint (CloudCap standard capacity on 2026-03-07) in the scoped completion handoff. Close “Migrate /v1/auth traffic to /v2/auth and retire v1.” only after the business state and readbacks are complete: close ENG-2402 only once the work is actually done, not before.",
       "employee_outcome": "Migrate /v1/auth traffic to /v2/auth and retire v1.",
-      "investigate": "Build the causal case for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the operative approval policy, and the PagerDuty change-event history; finally test the competing explanation against the exact operating document, the current operating standard (for api), and the served API surface (api-gateway). All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Prove that the same outcome for “Migrate /v1/auth traffic to /v2/auth and retire v1.” is deliverable through storefront-web, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 17 observed less 4 reserved for api-gateway leaves 13 usable and a 3-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-07 customer date.",
-      "verify": "Prove the observable result for “Migrate /v1/auth traffic to /v2/auth and retire v1.” after the transition: the retirement pull request must have passed all four CI stages including regression; no deployment may trip a new alarm; reopen current code-review state (storefront-web), the deployment ledger (storefront-web), current code-review state (api-gateway), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item and confirm the persisted result. After the last guarded transition for “Migrate /v1/auth traffic to /v2/auth and retire v1.”, reopen current code-review state (storefront-web), the deployment ledger (storefront-web), current code-review state (api-gateway), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item, then reopen the completion conversation so persistence and communication are both proven."
+      "investigate": "Build the causal case for “Migrate /v1/auth traffic to /v2/auth and retire v1.”: first resolve the same work across the authoritative Jira work item, the cross-tracker link registry, and the linked GitHub issue population; then use the operating-control index and the exact control revision to select the effective rule over the retired shortcut; reconcile ownership, approval, and reported context through the case-room conversation, the operative approval policy, and the PagerDuty change-event history; finally test the competing explanation against the exact operating document, the current operating standard (for api), and the served API surface (api-gateway). All 20 exact causal facts must be present inside the 26-read investigation before they support this outcome: /v1/auth must be retired in production; /v2/auth must remain active; /v1/auth must serve 0% traffic; /v2/auth must serve 100% traffic; the consumer storefront-web must be migrated to auth_api_version=v2 in production. Prove that the same outcome for “Migrate /v1/auth traffic to /v2/auth and retire v1.” is deliverable through api-gateway, using scattered records: 4 healthy replicas per zone across 4 zones means 16 required; 17 observed less 4 reserved for analytics-worker leaves 13 usable and a 3-replica gap. Reconcile that gap with CloudCap's 2026-03-07 standard and 2026-03-04 expedited deliveries, the published change windows, and the independent 2026-03-07 customer date.",
+      "verify": "Prove the observable result for “Migrate /v1/auth traffic to /v2/auth and retire v1.” after the transition: the retirement pull request must have passed all four CI stages including regression; no deployment may trip a new alarm; reopen current code-review state (storefront-web), current code-review state (api-gateway), the deployment ledger (storefront-web), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item and confirm the persisted result. After the last guarded transition for “Migrate /v1/auth traffic to /v2/auth and retire v1.”, reopen current code-review state (storefront-web), current code-review state (api-gateway), the deployment ledger (storefront-web), the deployment ledger (api-gateway), the served API surface (api-gateway), and the employee work item, then reopen the completion conversation so persistence and communication are both proven."
     },
     "score_weights": {
       "analysis.capacity_plan": 9,
@@ -2630,5 +2630,5 @@
   },
   "task_id": "dob100-017-auth-v1-to-v2",
   "task_name": "Migrate /v1/auth traffic to /v2/auth and retire v1.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-018-rca-payments-retry.json

@@ -1547,7 +1547,7 @@
     "service": "payments",
     "source_split": "train",
     "source_task_id": "tsk_rca_payments_retry",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2470,5 +2470,5 @@
   },
   "task_id": "dob100-018-rca-payments-retry",
   "task_name": "Payments error rate.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-019-rca-catalog-n-plus-one.json

@@ -1548,7 +1548,7 @@
     "service": "catalog",
     "source_split": "train",
     "source_task_id": "tsk_rca_catalog_n_plus_one",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2471,5 +2471,5 @@
   },
   "task_id": "dob100-019-rca-catalog-n-plus-one",
   "task_name": "Catalog pricing latency.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-020-rca-notifications-timeout.json

@@ -1548,7 +1548,7 @@
     "service": "notifications",
     "source_split": "train",
     "source_task_id": "tsk_rca_notifications_timeout",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2471,5 +2471,5 @@
   },
   "task_id": "dob100-020-rca-notifications-timeout",
   "task_name": "Notification delivery failures.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-021-rca-inventory-pool.json

@@ -1547,7 +1547,7 @@
     "service": "inventory",
     "source_split": "train",
     "source_task_id": "tsk_rca_inventory_pool",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2470,5 +2470,5 @@
   },
   "task_id": "dob100-021-rca-inventory-pool",
   "task_name": "Inventory reservation failures.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-022-rca-inventory-migrator-security-context.json

@@ -1547,7 +1547,7 @@
     "service": "inventory",
     "source_split": "train",
     "source_task_id": "tsk_rca_inventory_migrator_security_context",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2468,5 +2468,5 @@
   },
   "task_id": "dob100-022-rca-inventory-migrator-security-context",
   "task_name": "Inventory counts disagree with the database.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-023-rca-inventory-missing-role.json

@@ -1545,7 +1545,7 @@
     "service": "inventory",
     "source_split": "heldout",
     "source_task_id": "tsk_rca_inventory_missing_role",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2466,5 +2466,5 @@
   },
   "task_id": "dob100-023-rca-inventory-missing-role",
   "task_name": "The inventory report has never produced output.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-024-attr-three-at-once.json

@@ -1576,7 +1576,7 @@
     "service": "checkout",
     "source_split": "train",
     "source_task_id": "tsk_attr_three_at_once",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2511,5 +2511,5 @@
   },
   "task_id": "dob100-024-attr-three-at-once",
   "task_name": "Three alarms in twenty minutes - is this one incident or three?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-025-rca-catalog-gc-thrash.json

@@ -1546,7 +1546,7 @@
     "service": "catalog",
     "source_split": "heldout",
     "source_task_id": "tsk_rca_catalog_gc_thrash",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2469,5 +2469,5 @@
   },
   "task_id": "dob100-025-rca-catalog-gc-thrash",
   "task_name": "Catalog latency comes in waves.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-026-rca-storefront-traffic-flood.json

@@ -1545,7 +1545,7 @@
     "service": "storefront-web",
     "source_split": "train",
     "source_task_id": "tsk_rca_storefront_traffic_flood",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2466,5 +2466,5 @@
   },
   "task_id": "dob100-026-rca-storefront-traffic-flood",
   "task_name": "The homepage is taking unusual load.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-027-rca-analytics-untolerated-taint.json

@@ -1545,7 +1545,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_rca_analytics_untolerated_taint",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2464,5 +2464,5 @@
   },
   "task_id": "dob100-027-rca-analytics-untolerated-taint",
   "task_name": "The nightly reconciliation never runs.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-028-rca-media-recreate-strategy.json

@@ -1548,7 +1548,7 @@
     "service": "media-service",
     "source_split": "heldout",
     "source_task_id": "tsk_rca_media_recreate_strategy",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2469,5 +2469,5 @@
   },
   "task_id": "dob100-028-rca-media-recreate-strategy",
   "task_name": "Media-service is briefly unavailable on every release.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-029-rca-inventory-unbound-storage.json

@@ -1547,7 +1547,7 @@
     "service": "inventory",
     "source_split": "train",
     "source_task_id": "tsk_rca_inventory_unbound_storage",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2468,5 +2468,5 @@
   },
   "task_id": "dob100-029-rca-inventory-unbound-storage",
   "task_name": "Inventory is one replica short.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-030-rcn-distinct-checkout-bugs.json

@@ -1539,7 +1539,7 @@
     "service": "checkout",
     "source_split": "heldout",
     "source_task_id": "tsk_rcn_distinct_checkout_bugs",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2466,5 +2466,5 @@
   },
   "task_id": "dob100-030-rcn-distinct-checkout-bugs",
   "task_name": "How many distinct open checkout bugs do we have?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-031-impl-backoff.json

@@ -1537,7 +1537,7 @@
     "service": "payments",
     "source_split": "train",
     "source_task_id": "tsk_impl_backoff",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2442,5 +2442,5 @@
   },
   "task_id": "dob100-031-impl-backoff",
   "task_name": "Implement the payments retry backoff schedule.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-032-impl-cachekey.json

@@ -1537,7 +1537,7 @@
     "service": "search",
     "source_split": "train",
     "source_task_id": "tsk_impl_cachekey",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2442,5 +2442,5 @@
   },
   "task_id": "dob100-032-impl-cachekey",
   "task_name": "Implement the search cache key.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-033-impl-chunk.json

@@ -1537,7 +1537,7 @@
     "service": "payments",
     "source_split": "train",
     "source_task_id": "tsk_impl_chunk",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2442,5 +2442,5 @@
   },
   "task_id": "dob100-033-impl-chunk",
   "task_name": "Implement settlement batch chunking.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-034-impl-ratelimit.json

@@ -1535,7 +1535,7 @@
     "service": "api-gateway",
     "source_split": "heldout",
     "source_task_id": "tsk_impl_ratelimit",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2438,5 +2438,5 @@
   },
   "task_id": "dob100-034-impl-ratelimit",
   "task_name": "Implement per-client rate limiting at the edge.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-035-port-close-backlog-issues.json

@@ -548,14 +548,14 @@
       "source": "the PagerDuty change-event history"
     },
     {
-      "bytes": 68743,
+      "bytes": 68762,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current work-item population",
       "path": "task_files/dob100-035-port-close-backlog-issues/material/10-the-current-work-item-population.json",
       "query_scope": {},
-      "sha256": "f075f0cc22dd832b95008b44537ed8e2011f30b46bac66adfd20e2c5b5553844",
+      "sha256": "e022aab5b4ae8e13913f43d6cb72ba4200445034fd7273c4e4c9cef05248bc78",
       "source": "the current work-item population"
     },
     {
@@ -691,7 +691,7 @@
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-035-port-close-backlog-issues/51-agent-visible-asset-manifest.json",
-      "sha256": "261f0fd0e3520a6d98d77af69a1076a255dd3c117af7acbdc13e62af0022e934",
+      "sha256": "d0d44706fa7640eaf1dd8b3062bc759c437aa9485ef762088512efca132ad278",
       "source": "release builder"
     }
   ],
@@ -1523,7 +1523,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_close_backlog_issues",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2455,5 +2455,5 @@
   },
   "task_id": "dob100-035-port-close-backlog-issues",
   "task_name": "Empty the Backlog before sprint planning.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-036-port-close-blocked-issues.json

@@ -561,14 +561,14 @@
       "source": "the current Jira population"
     },
     {
-      "bytes": 68743,
+      "bytes": 68762,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current work-item population",
       "path": "task_files/dob100-036-port-close-blocked-issues/material/11-the-current-work-item-population.json",
       "query_scope": {},
-      "sha256": "5ffd46dc5a77a0ecb3c5d1e7bc18dfbb36b9de0cb645d3d4a063bedced18a4cf",
+      "sha256": "55e246e7aff4a0bae65bbc01ac7d62ed935ff1eaab9369e7a374e22af8571b8b",
       "source": "the current work-item population"
     },
     {
@@ -688,7 +688,7 @@
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-036-port-close-blocked-issues/51-agent-visible-asset-manifest.json",
-      "sha256": "6d3c3b5585a953e9bc1f044f67c28f31c897f15281dd1ebfb9ffd5f02a9de7bd",
+      "sha256": "b846614c23df3e328cbe75aba8dae4062b9a2fb1c2d540999023eed591c662c7",
       "source": "release builder"
     }
   ],
@@ -1520,7 +1520,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_close_blocked_issues",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2434,5 +2434,5 @@
   },
   "task_id": "dob100-036-port-close-blocked-issues",
   "task_name": "Clear the Blocked column.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-037-port-copy-priority-issues.json

@@ -574,14 +574,14 @@
       "source": "the current Jira population"
     },
     {
-      "bytes": 68743,
+      "bytes": 68762,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current work-item population",
       "path": "task_files/dob100-037-port-copy-priority-issues/material/12-the-current-work-item-population.json",
       "query_scope": {},
-      "sha256": "8f740317c0be16a84134d6ff77df32911117c333c7fdf1236298da5aba9d607c",
+      "sha256": "5d2101455ec55e6aef0187a5e465d698c8002a0d75e763f916c7eff63cd7758f",
       "source": "the current work-item population"
     },
     {
@@ -688,7 +688,7 @@
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-037-port-copy-priority-issues/51-agent-visible-asset-manifest.json",
-      "sha256": "956113f7ffd13f7a52eb7679cf3643716d2ec7b67f64554e6fa9c81d4468abff",
+      "sha256": "2804c449c85aefb2d4e6af64d34b5015876325836cfe34a89fd8d48b256cea21",
       "source": "release builder"
     }
   ],
@@ -1523,7 +1523,7 @@
     "service": "api-gateway",
     "source_split": "heldout",
     "source_task_id": "tsk_port_copy_priority_issues",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2454,5 +2454,5 @@
   },
   "task_id": "dob100-037-port-copy-priority-issues",
   "task_name": "Mirror priority GitHub issues onto the board.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-038-port-count-inflight-work.json

@@ -547,14 +547,14 @@
       "source": "the PagerDuty change-event history"
     },
     {
-      "bytes": 68743,
+      "bytes": 68762,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current work-item population",
       "path": "task_files/dob100-038-port-count-inflight-work/material/10-the-current-work-item-population.json",
       "query_scope": {},
-      "sha256": "26f6bf47a23c870b848602aab8f6045dc5062f3b6037d418c26cc4f934efbea3",
+      "sha256": "6d3a939e89b48a23d13af155c953e40420a1521b6d0abcf0b0a5257b795c493c",
       "source": "the current work-item population"
     },
     {
@@ -687,7 +687,7 @@
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-038-port-count-inflight-work/51-agent-visible-asset-manifest.json",
-      "sha256": "b77857867a7e77dda63361fc13370858f935092d69205eebb3691aee37ef5457",
+      "sha256": "9e637b84a56521931475034485ef259144b4d792ebc451877233fe88051d0ff1",
       "source": "release builder"
     }
   ],
@@ -1531,7 +1531,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_count_inflight_work",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2418,5 +2418,5 @@
   },
   "task_id": "dob100-038-port-count-inflight-work",
   "task_name": "How much high-priority work is in flight?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-039-port-count-unowned-work.json

@@ -547,14 +547,14 @@
       "source": "the PagerDuty change-event history"
     },
     {
-      "bytes": 68743,
+      "bytes": 68762,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current work-item population",
       "path": "task_files/dob100-039-port-count-unowned-work/material/10-the-current-work-item-population.json",
       "query_scope": {},
-      "sha256": "c277cecc29b18685809302266fc074f089ad0910530ddcbb1f7b496527ba4f36",
+      "sha256": "d10f23f9464576e7b32c64be866e1291ef90989c0ea6a084861187b7f8b623e5",
       "source": "the current work-item population"
     },
     {
@@ -687,7 +687,7 @@
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-039-port-count-unowned-work/51-agent-visible-asset-manifest.json",
-      "sha256": "4776dfa5c994e38579ef912affd7030b08ab7eadaaa2483d35fa319c85d423e3",
+      "sha256": "99bd8be6fd2e3b37bc45c5415ef6aa48477e51e4c06151375ba2c8be2eb91d08",
       "source": "release builder"
     }
   ],
@@ -1531,7 +1531,7 @@
     "service": "api-gateway",
     "source_split": "heldout",
     "source_task_id": "tsk_port_count_unowned_work",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2418,5 +2418,5 @@
   },
   "task_id": "dob100-039-port-count-unowned-work",
   "task_name": "How much unassigned work is still live?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-040-port-dedupe-linked-issues.json

@@ -585,14 +585,14 @@
       "source": "the current Jira population"
     },
     {
-      "bytes": 68743,
+      "bytes": 68762,
       "evidence_role": "decision-controlling sandbox export",
       "kind": "json",
       "material": true,
       "material_reason": "the current work-item population",
       "path": "task_files/dob100-040-port-dedupe-linked-issues/material/13-the-current-work-item-population.json",
       "query_scope": {},
-      "sha256": "f18d567f242f45b124fc8e711a5dad1cf53902704138a1ef7c35ca8863049221",
+      "sha256": "9f895c5147da7930f608caabc2898c8c3c299650781c06e8ce1317af045dc653",
       "source": "the current work-item population"
     },
     {
@@ -688,7 +688,7 @@
       "kind": "json",
       "material": false,
       "path": "task_files/dob100-040-port-dedupe-linked-issues/51-agent-visible-asset-manifest.json",
-      "sha256": "31fce9c210979ee641642a26e0f008c1af8c9ea9d3e5d7cba4c811044bcb889e",
+      "sha256": "f9eb6bad59070c53f6e6ec12487c9b7bbb2c50847d2db1145823ab41c2349675",
       "source": "release builder"
     }
   ],
@@ -1521,7 +1521,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_dedupe_linked_issues",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2450,5 +2450,5 @@
   },
   "task_id": "dob100-040-port-dedupe-linked-issues",
   "task_name": "Close the tickets that duplicate other trackers.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-041-port-escalate-to-gateway-oncall.json

@@ -1532,7 +1532,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_escalate_to_gateway_oncall",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2419,5 +2419,5 @@
   },
   "task_id": "dob100-041-port-escalate-to-gateway-oncall",
   "task_name": "Who do we page for the gateway right now?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-042-port-high-priority-since.json

@@ -1524,7 +1524,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_high_priority_since",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2436,5 +2436,5 @@
   },
   "task_id": "dob100-042-port-high-priority-since",
   "task_name": "Chase the recent high-priority issues in #eng.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-043-analytics-batch-size.json

@@ -1560,7 +1560,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_analytics_batch_size",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2512,5 +2512,5 @@
   },
   "task_id": "dob100-043-analytics-batch-size",
   "task_name": "Analytics rollups run in batches large enough to amplify memory pressure.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-044-analytics-prefetch.json

@@ -1576,7 +1576,7 @@
     "service": "analytics-worker",
     "source_split": "train",
     "source_task_id": "tsk_analytics_prefetch",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2582,5 +2582,5 @@
   },
   "task_id": "dob100-044-analytics-prefetch",
   "task_name": "Analytics worker restarting under queue load.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-045-checkout-payments-timeout.json

@@ -1569,7 +1569,7 @@
     "service": "payments",
     "source_split": "train",
     "source_task_id": "tsk_checkout_payments_timeout",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2542,5 +2542,5 @@
   },
   "task_id": "dob100-045-checkout-payments-timeout",
   "task_name": "Checkout waits 8s on the payments call.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-046-inventory-pool.json

@@ -1582,7 +1582,7 @@
     "service": "inventory",
     "source_split": "heldout",
     "source_task_id": "tsk_inventory_pool",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2607,5 +2607,5 @@
   },
   "task_id": "dob100-046-inventory-pool",
   "task_name": "Inventory reservations failing under peak traffic.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-047-notifications-timeout.json

@@ -1576,7 +1576,7 @@
     "service": "notifications",
     "source_split": "train",
     "source_task_id": "tsk_notifications_timeout",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2582,5 +2582,5 @@
   },
   "task_id": "dob100-047-notifications-timeout",
   "task_name": "Notification delivery failures from hung SMTP calls.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-048-port-count-open-priority.json

@@ -1532,7 +1532,7 @@
     "service": "api-gateway",
     "source_split": "train",
     "source_task_id": "tsk_port_count_open_priority",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2422,5 +2422,5 @@
   },
   "task_id": "dob100-048-port-count-open-priority",
   "task_name": "How many open priority issues are there?",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-049-payments-retry.json

@@ -1584,7 +1584,7 @@
     "service": "payments",
     "source_split": "train",
     "source_task_id": "tsk_payments_retry",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2596,5 +2596,5 @@
   },
   "task_id": "dob100-049-payments-retry",
   "task_name": "Payments error rate breaching the 1% SLO.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }

tasks/dob100-050-payments-retry-from-code.json

@@ -1586,7 +1586,7 @@
     "service": "payments",
     "source_split": "heldout",
     "source_task_id": "tsk_payments_retry_from_code",
-    "version": "3.2.4"
+    "version": "3.2.5"
   },
   "post_write_verifications": [
     {
@@ -2599,5 +2599,5 @@
   },
   "task_id": "dob100-050-payments-retry-from-code",
   "task_name": "Payments: eliminate the permanent-failure path on notification timeouts.",
-  "world_id": "env_software_devops_0ec42f0f"
+  "world_id": "env_software_devops_5a8aaf25"
 }