{
  "context_files": [],
  "gold_output": {
    "expected_final_state_checks": {
      "correctness": [
        "diagnosis_submitted",
        "service_localized",
        "fault_type_correct",
        "offending_key_correct",
        "scoped_change_no_fabricated_data",
        "world_invariants_intact"
      ],
      "deployment": [
        "investigation_was_read_only"
      ],
      "quality": [
        "evidence_recorded",
        "efficient_investigation",
        "ticket_closed",
        "closed_after_the_work",
        "no_new_hardcoded_secrets",
        "no_unproductive_ci_loops"
      ]
    },
    "ground_truth_submissions": [
      {
        "arguments": {
          "evidence": "node-c1 is Ready=Unknown with a kernel soft lockup on CPU#3 and stopped posting node status 14 minutes ago; notifications-1b7d-hh88 still reports Running because the kubelet stopped reporting, not the pod, so pod phase alone says the service is healthy while it is unreachable",
          "fault_detected": true,
          "fault_type": "node_unhealthy",
          "offending_key": "node-c1",
          "scope": "notifications-unreachable",
          "service": "notifications"
        },
        "tool": "submit_diagnosis"
      }
    ],
    "note": "Acceptance is state-based: every correctness and deployment check must hold over the final world database and its append-only audit log."
  },
  "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-127 — Root cause: notifications are not being delivered\n\nGet to the bottom of notifications-unreachable: not just which service, but the mechanism and the exact setting responsible. The service's own code is not necessarily where this lives — confirm it against the state of the system rather than inferring it from the symptom alone. Submit your finding under scope 'notifications-unreachable' with the responsible service, the fault type, the offending key, and your evidence.\n\nProcedure: read the production logs and the error tracker, inspect the deployed configuration, and then look one layer down - at the cluster the service runs on, its nodes, its pods and their events - because a fault there leaves no trace in the service's own code or metrics. Confirm the mechanism against that state before submitting.",
  "metadata": {
    "benchmark": "DevOpsBench-100",
    "category": "aiops_analysis",
    "code_license": "Apache-2.0",
    "curation_rationale": [
      "aiops_analysis",
      "expert",
      "10-call-oracle",
      "curated",
      "hardest-of-category-quota",
      "controls-rejected:pristine"
    ],
    "data_license": "CC-BY-4.0",
    "difficulty": "expert",
    "grading": "deterministic",
    "guided_instruction_available": true,
    "harbor_name": "blobfishai/dob100-005-rca-notifications-node-deadlock",
    "llm_judge": false,
    "origin": "curated",
    "reference_tool_calls": 10,
    "required_tools": [
      "get_service",
      "get_ticket",
      "k8s_events_list",
      "k8s_nodes_list",
      "k8s_pods_list",
      "list_error_events",
      "query_metrics",
      "search_logs",
      "submit_diagnosis",
      "update_ticket"
    ],
    "source_split": "train",
    "source_task_id": "tsk_rca_notifications_node_deadlock",
    "version": "1.0.0"
  },
  "prompt": "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-127 — Root cause: notifications are not being delivered\n\nGet to the bottom of notifications-unreachable: not just which service, but the mechanism and the exact setting responsible. The service's own code is not necessarily where this lives — confirm it against the state of the system rather than inferring it from the symptom alone. Submit your finding under scope 'notifications-unreachable' with the responsible service, the fault type, the offending key, and your evidence.",
  "rubric": {
    "checks": {
      "correctness": [
        "diagnosis_submitted",
        "service_localized",
        "fault_type_correct",
        "offending_key_correct",
        "scoped_change_no_fabricated_data",
        "world_invariants_intact"
      ],
      "deployment": [
        "investigation_was_read_only"
      ],
      "quality": [
        "evidence_recorded",
        "efficient_investigation",
        "ticket_closed",
        "closed_after_the_work",
        "no_new_hardcoded_secrets",
        "no_unproductive_ci_loops"
      ]
    },
    "grading": "deterministic",
    "llm_judge": false,
    "pass_rule": "every correctness and deployment check holds over the final world state and audit log",
    "score_weights": {
      "correctness": 0.6,
      "deployment": 0.3,
      "quality": 0.1
    },
    "type": "deterministic",
    "verifier": "verifiers/verify_dob100-005-rca-notifications-node-deadlock.py"
  },
  "task_id": "dob100-005-rca-notifications-node-deadlock",
  "task_name": "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(...).",
  "world_id": "env_software_devops_0ec42f0f"
}