Experimentspijev
New
pijev
pijev sends the same ticket state with several typed Choice questions that vary only the order of the same support-team criteria.
Added to Jevfast
How it uses Jev
pijev sends the same ticket state with several typed Choice questions that vary only the order of the same support-team criteria. It aligns returned probabilities by team, averages them, and returns the highest-mean team through the SDK-compatible response. The README documents both a two-order comparison (`forward`, `reverse`) and the pijev request (`team`); the shown option IDs are `billing`, `technical`, and `account`.
What Jev decides
Illustrative support-team permutation requestExample answers · not a recorded Jev response · Source ↗
Question 1 · team
YOUR APP
INSTRUCTION
Choose the best primary support team for the ticket.
STATE
A support ticket says a recent plan upgrade was paid, but dashboard access still reports the subscription as inactive.
JEV · CHOICE
- billing
- technical
- account
App workflow
- Build the request
The caller supplies a ticket state and typed Choice criteria through the familiar TypeSafe client interface.
- Expand and evaluate
pijev creates a balanced set of option orderings and asks them together in one System One request.
- Aggregate the result
It aligns probabilities by option, averages them, and returns the original question name with the aggregated answer.
Why it is interesting
It treats option-order sensitivity as a nuisance variable and averages across permutations in one request. Its guarantee is about convex scoring loss versus a random included prediction, not an unconditional calibration or accuracy guarantee.