Our summary
Some software needs a choice, not a written reply. QubitTool Tech Team explains how Jev can select a team, estimate the chance of yes or judge an ordered scale from supplied text. Restricting the possible answers makes them easier for code to handle, but the model can still select the wrong answer.
The Go example sends one support message to hosted Jev. It sets a deadline, limits the response size and checks the model version, answer type, allowed labels and probabilities. It prints a team only when the example's routing conditions pass; otherwise it prints a review result or reports an error.
Confidence is calculated from the same probabilities the answer supplies. Checking both does not create two independent safety checks. The code was inspected, not compiled or run, and implements no retries. A printed route neither performs the business action nor checks whether that action is permitted.
Key takeaways
- Use fixed answer choices to control output shape, not to claim that an answer is true or immune to misleading instructions.
- Test routing cutoffs on your own labeled messages. For this three-option example, the probability cutoff is stricter than its related confidence cutoff.
- Keep missing evidence, uncertain meaning and service failure separate. The example makes one attempt; retry scheduling and permission checks require additional code.