Combine declared decisions

Send related but distinct questions in one request and handle each returned answer separately. A decided answer includes its declared selection and any available evidence; unresolved and refused remain non-action outcomes.

{
  "state": {"parcel": "The parcel is delayed and the customer asks for an update."},
  "questions": {
    "topic": {
      "type": "choice",
      "instructions": {"question": "Which team should handle this request?"},
      "criteria": {
        "delivery": "Parcel status, late delivery, or tracking",
        "billing": "Charges, invoices, refunds, or subscriptions"
      }
    },
    "asks_for_update": {
      "type": "noul",
      "instructions": {"question": "Does the customer ask for an update?"},
      "criteria": {
        "true": "The customer asks for current parcel or delivery information",
        "false": "The customer does not ask for current parcel or delivery information"
      }
    }
  }
}

The caller defines what to do with each outcome. Do not combine compatibility confidence fields into a score or treat them as calibrated probabilities. Apply your application's authorization and policy before any external action. See the /v1/systemone reference for the request and response contract.