Speculative Fan-Out Question Battery

{
  "model": "jev-latest",
  "state": {
    "submission": "{{submission-text}}",
    "submitter_plan": "{{submitter-plan}}"
  },
  "questions": {
    "category": {
      "type": "choice",
      "instructions": "What kind of submission is this?",
      "criteria": {
        "bug_report": "Something is broken or behaving unexpectedly",
        "feature_request": "Asks for new behaviour that does not exist",
        "billing": "Charges, invoices, refunds, plan changes",
        "question": "Asks how something works",
        "other": "None of the above"
      }
    },
    "bug_severity": {
      "type": "score",
      "instructions": "If this is a bug, how severe is it?",
      "criteria": [
        "Cosmetic, no functional impact",
        "Broken or degraded feature, but a workaround exists",
        "Core feature unusable, no workaround",
        "Data loss, security exposure, or outage"
      ]
    },
    "has_repro_steps": {
      "type": "noul",
      "instructions": "The submission includes steps someone else could follow to reproduce the problem"
    },
    "refund_requested": {
      "type": "noul",
      "instructions": "The submitter explicitly asks for money back"
    },
    "feature_already_exists": {
      "type": "noul",
      "instructions": "The requested capability is something the product description in the state says already exists"
    },
    "needs_reply_today": {
      "type": "noul",
      "instructions": "The submission is time-sensitive enough that a reply within one business day matters"
    }
  }
}

One request, every branch's questions included, then the code reads only what applies: bug_report uses bug_severity and has_repro_steps; billing uses refund_requested; feature_request uses feature_already_exists; everything uses needs_reply_today. Extra questions barely change latency, so ask them all up front rather than making a second round trip per branch.