Advanced Structure

Structured criteria let an application declare the phrases associated with each option. They do not replace application policy or guarantee a refusal.

Siliqun Rotor supports structured criteria for Choice options, Score levels, and Noul criteria.

Structured criteria fields

{
  "state": {"request": "Pause my subscription for a month"},
  "questions": {
    "change": {
      "type": "choice",
      "instructions": {"question": "What account change is requested?"},
      "criteria": {
        "close_account": {
          "what": "Requests to close or terminate an account",
          "examples": ["Close my account", "Delete my profile"],
          "not_for": ["Temporarily pause a subscription"]
        },
        "pause_subscription": {
          "what": "Requests to pause a subscription temporarily",
          "examples": ["Pause my subscription for a month"]
        }
      }
    }
  }
}

How these fields are read

what and examples contribute positive criteria.
not_for is excluded from the positive criteria. It does not, by itself, install a veto or guarantee a refusal for a matching request.

If an exclusion is required, declare and evaluate that condition explicitly, then enforce the application's policy before executing an action. See the tool-routing guide for the separate not_for behavior in declared tool routing.