Noul

A statement score from 0 to 1: check whether a fact is present, a rule applies, or a condition is met.

State one condition

type: “noul” suits a question with two sides: yes and no. You can omit criteria or provide descriptions with the keys true and false. If a question contains several independent conditions, it is better to separate them.

Clarify whether you are checking for a fact in the context or drawing a conclusion from a rule. “Is a return mentioned?” and “Is a return allowed?” are different tasks.

Noul in a complete request

{
  "state": "Card payment is not working. Cash on delivery is available. The customer asks for help placing an order.",
  "questions": {
    "alternative": {
      "type": "noul",
      "instructions": "Does the context specify another available payment method?",
      "criteria": {
        "true": "Another payment method is available",
        "false": "No alternative is specified, or it is unavailable"
      }
    }
  }
}

Read noul

answers.alternative.noul is a number from 0 to 1. Higher values indicate stronger support for true. Separate confidence and probabilities fields for Noul are not part of this contract.

You can use 0.5 as an initial experimental threshold, but a production threshold depends on the consequences of errors. You can leave a manual-review zone between acceptance and rejection thresholds.

Illustration of answers.alternative; not a run result

{
  "type": "noul",
  "noul": 0.94
}

The example value 0.94 demonstrates the numeric format. It is not a measured probability of success for your workflow.

Test negation and missing information

Include texts with words such as “not”, “previously”, “so far”, and conditional statements.
Distinguish between a fact not being mentioned and an explicit denial, if that matters for your task.
Test quotations, forwarded messages, and conflicting information.
Keep human review available for consequential actions.