[
  {
    "id": "dev-01",
    "domain": "development",
    "state": "A date-sorting function compares dates as text and orders them incorrectly; the application logic needs a fix. All required release checks currently pass. An analyst cannot finish a report using the sort, but exporting and sorting in a spreadsheet is a working workaround.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which kind of change is needed to address the reported defect? Choose unknown when the state does not establish a category.",
        "criteria": {
          "implementation": "Fix executable application logic.",
          "tests": "Fix or add automated test coverage or assertions.",
          "documentation": "Fix written instructions or documentation.",
          "unknown": "The information is insufficient to identify the kind of change."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Is at least one required release check currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "implementation",
      "risk": false,
      "impact": 1
    },
    "rationale": "The defect is executable logic; checks pass; a blocked report has an explicit workaround."
  },
  {
    "id": "dev-02",
    "domain": "development",
    "state": "The checkout implementation is correct, but its automated test never asserts the total and needs that assertion added. All required release checks pass. No work or user workflow is currently blocked.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which kind of change is needed to address the reported defect? Choose unknown when the state does not establish a category.",
        "criteria": {
          "implementation": "Fix executable application logic.",
          "tests": "Fix or add automated test coverage or assertions.",
          "documentation": "Fix written instructions or documentation.",
          "unknown": "The information is insufficient to identify the kind of change."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Is at least one required release check currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "tests",
      "risk": false,
      "impact": 0
    },
    "rationale": "The requested change is a test assertion, no check fails, and nothing is blocked."
  },
  {
    "id": "dev-03",
    "domain": "development",
    "state": "The setup guide gives an obsolete command; the executable tooling is correct. The required documentation link check currently fails. New engineers cannot complete setup and no working workaround exists.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which kind of change is needed to address the reported defect? Choose unknown when the state does not establish a category.",
        "criteria": {
          "implementation": "Fix executable application logic.",
          "tests": "Fix or add automated test coverage or assertions.",
          "documentation": "Fix written instructions or documentation.",
          "unknown": "The information is insufficient to identify the kind of change."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Is at least one required release check currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "documentation",
      "risk": true,
      "impact": 2
    },
    "rationale": "Written instructions need repair, a required check fails, and setup is blocked without a workaround."
  },
  {
    "id": "dev-04",
    "domain": "development",
    "state": "A required release check currently fails, but its name, output, and logs are unavailable. There is no evidence about what must change. Release preparation is blocked; using the explicitly approved previous build is a working workaround.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which kind of change is needed to address the reported defect? Choose unknown when the state does not establish a category.",
        "criteria": {
          "implementation": "Fix executable application logic.",
          "tests": "Fix or add automated test coverage or assertions.",
          "documentation": "Fix written instructions or documentation.",
          "unknown": "The information is insufficient to identify the kind of change."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Is at least one required release check currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "unknown",
      "risk": true,
      "impact": 1
    },
    "rationale": "There is insufficient evidence to route the defect; a required check fails; a working workaround is stated."
  },
  {
    "id": "dev-05",
    "domain": "development",
    "state": "Application authorization logic rejects every valid editor role after a code change. The required authorization regression check currently fails. Editors cannot save any document and no working workaround exists.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which kind of change is needed to address the reported defect? Choose unknown when the state does not establish a category.",
        "criteria": {
          "implementation": "Fix executable application logic.",
          "tests": "Fix or add automated test coverage or assertions.",
          "documentation": "Fix written instructions or documentation.",
          "unknown": "The information is insufficient to identify the kind of change."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Is at least one required release check currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "implementation",
      "risk": true,
      "impact": 2
    },
    "rationale": "Application logic is the established defect, the required check fails, and saving is blocked without a workaround."
  },
  {
    "id": "dev-06",
    "domain": "development",
    "state": "The smoke test checks an obsolete button label and needs its assertion updated; the UI behavior is correct. A required check failed yesterday, but its latest run passed and all required release checks now pass. No work or user workflow is currently blocked.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which kind of change is needed to address the reported defect? Choose unknown when the state does not establish a category.",
        "criteria": {
          "implementation": "Fix executable application logic.",
          "tests": "Fix or add automated test coverage or assertions.",
          "documentation": "Fix written instructions or documentation.",
          "unknown": "The information is insufficient to identify the kind of change."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Is at least one required release check currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "tests",
      "risk": false,
      "impact": 0
    },
    "rationale": "Test code needs updating; the old failure is resolved; no workflow is blocked."
  },
  {
    "id": "ops-01",
    "domain": "devops",
    "state": "Tracing establishes that a new application-code null dereference causes checkout requests to fail now. Customers cannot complete checkout, and no working workaround exists.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which technical area is established as the cause of the incident? Choose unknown when the state does not establish a category.",
        "criteria": {
          "application": "An application-code defect is established.",
          "network": "A network, DNS, or routing fault is established.",
          "capacity": "Resource exhaustion or insufficient capacity is established.",
          "unknown": "The cause has not been established."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Are customer-facing requests currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "application",
      "risk": true,
      "impact": 2
    },
    "rationale": "An application defect is established, customer requests fail, and checkout has no workaround."
  },
  {
    "id": "ops-02",
    "domain": "devops",
    "state": "A bad DNS record is confirmed as the cause of customer-facing portal requests failing now. Customer report retrieval is blocked, but the documented secondary portal is working and provides the same reports.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which technical area is established as the cause of the incident? Choose unknown when the state does not establish a category.",
        "criteria": {
          "application": "An application-code defect is established.",
          "network": "A network, DNS, or routing fault is established.",
          "capacity": "Resource exhaustion or insufficient capacity is established.",
          "unknown": "The cause has not been established."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Are customer-facing requests currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "network",
      "risk": true,
      "impact": 1
    },
    "rationale": "DNS establishes a network cause; requests fail; the secondary portal is an explicit workaround."
  },
  {
    "id": "ops-03",
    "domain": "devops",
    "state": "A batch worker exhausted its disk space, which is the confirmed cause of a delayed internal export. Customer-facing requests are not failing. The export workflow is blocked, but running it on the spare worker is a working workaround.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which technical area is established as the cause of the incident? Choose unknown when the state does not establish a category.",
        "criteria": {
          "application": "An application-code defect is established.",
          "network": "A network, DNS, or routing fault is established.",
          "capacity": "Resource exhaustion or insufficient capacity is established.",
          "unknown": "The cause has not been established."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Are customer-facing requests currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "capacity",
      "risk": false,
      "impact": 1
    },
    "rationale": "Disk exhaustion establishes capacity; no customer request fails; a spare worker is a working workaround."
  },
  {
    "id": "ops-04",
    "domain": "devops",
    "state": "Monitoring shows customer-facing search requests failing now. The cause is not established: application, network, and capacity checks are inconclusive. Search-dependent work is blocked and no working workaround exists.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which technical area is established as the cause of the incident? Choose unknown when the state does not establish a category.",
        "criteria": {
          "application": "An application-code defect is established.",
          "network": "A network, DNS, or routing fault is established.",
          "capacity": "Resource exhaustion or insufficient capacity is established.",
          "unknown": "The cause has not been established."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Are customer-facing requests currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "unknown",
      "risk": true,
      "impact": 2
    },
    "rationale": "The cause is unknown, failures are current, and the blocked workflow has no workaround."
  },
  {
    "id": "ops-05",
    "domain": "devops",
    "state": "Yesterday a network routing fault was confirmed as the incident cause. It has been repaired. Customer-facing requests are not failing now, and no work or user workflow is currently blocked.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which technical area is established as the cause of the incident? Choose unknown when the state does not establish a category.",
        "criteria": {
          "application": "An application-code defect is established.",
          "network": "A network, DNS, or routing fault is established.",
          "capacity": "Resource exhaustion or insufficient capacity is established.",
          "unknown": "The cause has not been established."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Are customer-facing requests currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "network",
      "risk": false,
      "impact": 0
    },
    "rationale": "The established cause remains network, but the failure and blockage are resolved."
  },
  {
    "id": "ops-06",
    "domain": "devops",
    "state": "A confirmed application-code bug adds a harmless duplicate line to internal diagnostic logs. Customer-facing requests are not failing. No work or user workflow is currently blocked.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which technical area is established as the cause of the incident? Choose unknown when the state does not establish a category.",
        "criteria": {
          "application": "An application-code defect is established.",
          "network": "A network, DNS, or routing fault is established.",
          "capacity": "Resource exhaustion or insufficient capacity is established.",
          "unknown": "The cause has not been established."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Are customer-facing requests currently failing? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "application",
      "risk": false,
      "impact": 0
    },
    "rationale": "A code defect is established but causes neither customer-request failures nor workflow blockage."
  },
  {
    "id": "support-01",
    "domain": "support",
    "state": "The customer says: \"I cannot sign in, and password recovery also fails. There is no working workaround. Please have a human take over this case.\" Account access is the only reported problem.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which support team should own the stated problem? Choose unknown when the state does not establish a category.",
        "criteria": {
          "access": "Login, password, account access, or sign-in problems.",
          "billing": "Invoice, payment, or subscription charge problems.",
          "product": "A malfunction of a product feature other than access or billing.",
          "unknown": "The information is insufficient to determine the problem category."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Does the customer explicitly request that a human or manager take over the case? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "access",
      "risk": true,
      "impact": 2
    },
    "rationale": "The issue is access, human takeover is explicit, and sign-in is blocked without a workaround."
  },
  {
    "id": "support-02",
    "domain": "support",
    "state": "The customer says: \"Our invoice has the wrong company name. Please correct it; I do not need a human or manager to take over.\" No work or user workflow is currently blocked.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which support team should own the stated problem? Choose unknown when the state does not establish a category.",
        "criteria": {
          "access": "Login, password, account access, or sign-in problems.",
          "billing": "Invoice, payment, or subscription charge problems.",
          "product": "A malfunction of a product feature other than access or billing.",
          "unknown": "The information is insufficient to determine the problem category."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Does the customer explicitly request that a human or manager take over the case? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "billing",
      "risk": false,
      "impact": 0
    },
    "rationale": "Invoice correction belongs to billing; takeover is explicitly declined; nothing is blocked."
  },
  {
    "id": "support-03",
    "domain": "support",
    "state": "The customer says: \"The report-download button fails. Please ask a manager to take over.\" Report delivery is blocked in the product, but exporting through the working API provides the needed file. Login and billing work normally.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which support team should own the stated problem? Choose unknown when the state does not establish a category.",
        "criteria": {
          "access": "Login, password, account access, or sign-in problems.",
          "billing": "Invoice, payment, or subscription charge problems.",
          "product": "A malfunction of a product feature other than access or billing.",
          "unknown": "The information is insufficient to determine the problem category."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Does the customer explicitly request that a human or manager take over the case? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "product",
      "risk": true,
      "impact": 1
    },
    "rationale": "A product feature fails, a manager is requested, and the API supplies a working workaround."
  },
  {
    "id": "support-04",
    "domain": "support",
    "state": "The customer says: \"Something went wrong. Please have a human take over.\" They provide no product area, error, or symptom. They explicitly confirm that no work or user workflow is currently blocked.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which support team should own the stated problem? Choose unknown when the state does not establish a category.",
        "criteria": {
          "access": "Login, password, account access, or sign-in problems.",
          "billing": "Invoice, payment, or subscription charge problems.",
          "product": "A malfunction of a product feature other than access or billing.",
          "unknown": "The information is insufficient to determine the problem category."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Does the customer explicitly request that a human or manager take over the case? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "unknown",
      "risk": true,
      "impact": 0
    },
    "rationale": "No category is established; human takeover is requested; the stated impact is no blockage."
  },
  {
    "id": "support-05",
    "domain": "support",
    "state": "The customer says: \"My account sign-in is broken. I do not want a human or manager to take over.\" Their work is blocked on this account, but the approved temporary account works and restores access.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which support team should own the stated problem? Choose unknown when the state does not establish a category.",
        "criteria": {
          "access": "Login, password, account access, or sign-in problems.",
          "billing": "Invoice, payment, or subscription charge problems.",
          "product": "A malfunction of a product feature other than access or billing.",
          "unknown": "The information is insufficient to determine the problem category."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Does the customer explicitly request that a human or manager take over the case? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "access",
      "risk": false,
      "impact": 1
    },
    "rationale": "Access is the issue, takeover is declined, and the temporary account is an explicit workaround."
  },
  {
    "id": "support-06",
    "domain": "support",
    "state": "The customer says: \"The editor crashes whenever I save. Please continue automated troubleshooting; I am not asking for a human or manager.\" Saving work is blocked and no working workaround exists. Login and billing are unaffected.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Which support team should own the stated problem? Choose unknown when the state does not establish a category.",
        "criteria": {
          "access": "Login, password, account access, or sign-in problems.",
          "billing": "Invoice, payment, or subscription charge problems.",
          "product": "A malfunction of a product feature other than access or billing.",
          "unknown": "The information is insufficient to determine the problem category."
        }
      },
      "risk": {
        "type": "noul",
        "instructions": "Does the customer explicitly request that a human or manager take over the case? Use only current, explicitly stated facts; a past resolved condition does not count."
      },
      "impact": {
        "type": "score",
        "instructions": "Rate current workflow impact using the three ordered criteria. Consider only explicit blockage and working workaround facts, not alarming wording. The list positions are 0, 1, and 2.",
        "criteria": [
          "No work or user workflow is currently blocked.",
          "At least one work or user workflow is blocked, but an explicitly stated working workaround exists.",
          "At least one work or user workflow is blocked and no working workaround exists."
        ]
      }
    },
    "expected": {
      "route": "product",
      "risk": false,
      "impact": 2
    },
    "rationale": "The product feature fails, takeover is not requested, and saving has no workaround."
  }
]