Before you dive in
What you’ll find in the original
- Use Choice for a fixed menu, Score for an ordered scale, and Noul for the probability that a condition is true.
- Independent questions about the same state can run in parallel, but a decision that depends on an earlier answer must remain sequential.
- Keep thresholds and consequences in code: a valid typed answer can still be the wrong valid answer, so close probability distributions should trigger escalation.
Worth knowing
This is a conceptual explainer, not a benchmark. Its numerical probabilities are an illustrative routing example rather than measured production results.