State and evidence paths

state is the input evaluated by the questions in a System One request. It may be a string or structured JSON. Give the request only the information needed for its declared questions, and avoid including secrets that the application does not need to send.

{
  "state": {
    "ticket": {
      "message": "I was charged twice and want my money back."
    }
  },
  "questions": {
    "team": {
      "type": "choice",
      "instructions": {
        "question": "Which team should handle ticket.message?"
      },
      "criteria": {
        "billing": "Charges, invoices, refunds, or subscriptions",
        "orders": "Order status, delivery, cancellation, or returns"
      }
    }
  }
}

When the selected decision includes evidence, its path identifies the state location. start and end identify a UTF-8 byte range in the located source text. Compare the evidence with the same input bytes sent in the request; see evidence for details. A path and matching text show what the decision used, not whether the underlying claim is true.

Do not rely on natural-language instructions to enforce authorization or isolate sensitive fields. Apply access control before constructing the state and before executing any returned action.