Class TriageTicket
java.lang.Object
ai.redouble.examples.decision.TriageTicket
One decision. Much of what an application asks a model is a verdict among options the
code already knows: which team should take this ticket, is it urgent, how upset is the
customer. A decision model is built for exactly that: given a state and typed questions,
it writes no text and answers each question with a probability for every option, so every
answer is one of your options, the numbers show how clear-cut the call was, and code
branches on it directly. Output costs nothing, every question is answered in one round
trip, and a small one runs on your own machine.
Three shapes of question: Choice picks one of named options, Noul is a
statement that is true or false, Score places the state on an ordered scale. The
ids the questions go in under are the code's own and never reach the model, and the
questions ride a LinkedHashMap because option order can move the answer, so a
fixed order makes a run repeatable. DecisionCall is a job like any model call:
priced, admitted against the model's limits, recorded.
Run against Kev-9B on 2026-09-27, the ticket below came out billing 0.49 against shipping 0.44 with technical far behind, urgent 0.97, mood "very angry": the double charge and the late delivery both show, and code decides what to do with the near tie.
- Since:
- 0.1 (2026-09-27)
- Author:
- Andrey Santrosyan
-
Constructor Summary
Constructors -
Method Summary
-
Constructor Details
-
TriageTicket
public TriageTicket()
-
-
Method Details
-
main
-