Primitives· Last updated

How to read Jev probability distributions

Every Choice and Score answer includes probabilities.

When the top label is not enough

choice: "technical" with { technical: 0.51, billing: 0.49 } is a different system event from { technical: 0.98, billing: 0.02 }. Both can produce the same winner. Confidence is meant to distinguish them. If your domain cares about the runner-up (for example dual-queue routing), read the map.

Expected score

score is already the expectation over levels. You can recompute it from probabilities and legend for logging. Do not treat a fractional score as a physical measurement; see the numeric-calibration warning on jaggedness.

Logging

Store the versioned model, the full probabilities, and confidence. If an alias moves, you will want to know which ID produced the distribution you tuned against.

Sources

Public TypeSafe or adjacent documentation only. No private claims.