Why a condition cannot be answered yet because of a decision it reads, or null when it can.
Asked BEFORE evaluation, because evaluation cannot tell "no" from "not known": a missing answer
reads as undefined, and undefined === 'billing' is a confident, wrong false that would drop
the edge or lose the fork. So a condition that reads a failed decision, one below its question's
minConfidence, or one not given yet is refused evaluation and holds.
A use of decisions that names no step and question cannot be checked, so it holds too. The
validator refuses such a condition at submit; this is the backstop for one that bypassed it.
Why a condition cannot be answered yet because of a decision it reads, or
nullwhen it can.Asked BEFORE evaluation, because evaluation cannot tell "no" from "not known": a missing answer reads as
undefined, andundefined === 'billing'is a confident, wrongfalsethat would drop the edge or lose the fork. So a condition that reads a failed decision, one below its question'sminConfidence, or one not given yet is refused evaluation and holds.A use of
decisionsthat names no step and question cannot be checked, so it holds too. The validator refuses such a condition at submit; this is the backstop for one that bypassed it.