Confidence-Gated Routing

The answer tells you which branch. Confidence tells you whether to take it without a person.

Two numbers on a Choice

A Choice response carries:

• choice, the winning option
• probabilities, one weight per option
• confidence, derived from the shape of that distribution

Official confidence docs approximate three-option confidence as (3 × largest probability − 1) / 2. You can ignore that summary and threshold on a rule of your own, as long as the rule is in code where a reviewer can see it.

answer = response.answers["department"]

if answer.confidence >= 0.9:
    route(answer.choice, ticket)
elif answer.confidence >= 0.5:
    ask_for_confirmation(answer.choice, ticket)
else:
    route_to_human(ticket)

Those cutoffs are placeholders. Plot confidence against whether the label was right, on tickets you already know the answer to, before you ship either number.

Noul has one number

A Noul is already a probability that the statement is true. Branch on noul directly. Near 0.5 is the band you send to review. Phrase the statement so that a high value means the action you think it means. A question where "yes" means "do not escalate" is the failure mode in Limitations.

What the gate must do when the call fails

Confidence only exists on a successful response. A timeout, a 429, or a schema error needs its own branch. The public gates we reviewed fail closed: pi-jev-auto-mode blocks when the engine is missing or the body is malformed. Copy that for anything that deletes, pays, or sends.

Where else this shows up

• Composite scoring builds one number out of several Nouls, then puts the gate on that number.
• Classification using confidence is TypeSafe's cookbook for reporting a parent category when the leaf is uncertain.
• The patterns index lists the other official recipes that assume this gate.

Next: Choice or Composite scoring.