`POST /v1/systemone`

/v1/systemone accepts a state and named questions. Each answer reports one of three outcomes: decided, unresolved, or refused. A decided answer includes the evidence and source path returned by the selected engine.

Request

POST /v1/systemone
Content-Type: application/json

{
  "state": {"parcel": "Parcel is in transit"},
  "questions": {
    "status": {
      "type": "choice",
      "instructions": {"question": "What is the parcel status?"},
      "criteria": {
        "moving": "Parcel is in transit; in transit",
        "delivered": "Parcel has been delivered; delivered"
      }
    }
  }
}

state may be a string, object, or array. questions is an object keyed by caller-chosen answer IDs. Each question supports choice, score, or noul; see the primitive pages for the corresponding criteria shape. The model field is optional.

Response

The following is the captured conformance response for this request shape. The evidence offsets are UTF-8 byte offsets into the source string.

{
  "answers": {
    "status": {
      "type": "choice",
      "outcome": "decided",
      "choice": "moving",
      "index": 0,
      "evidence": [
        {"path":"parcel","start":0,"end":20,"text":"Parcel is in transit","criterion":"parcel is in transit","by":"exact"},
        {"path":"parcel","start":10,"end":20,"text":"in transit","criterion":"in transit","by":"exact"}
      ],
      "may_act": true,
      "confidence": 1.0,
      "probabilities": {"moving": 1.0},
      "engine": "tier1"
    }
  }
}

outcome and may_act are the action gate: only decided answers set may_act to true; unresolved and refused do not. Evidence records include the source path, byte start and end, located text, criterion, and the method identified by by. supported is returned for unresolved answers; unfound is returned for refusals. Treat confidence and probabilities as compatibility metadata when present; they are not calibration guarantees and are not the action gate.

Question IDs, engine, and optional trace fields can vary with the request and the serving stack. For the SDK request and response contract, see the SDK protocol.