An exclusive fork's edges with each path that reads a FAILED decision counted as not taken, in
every fork that has a satisfied path — so the satisfied one wins whatever its rank.
A failed decision call is a failed step, and a flow's failure handling is its outgoing paths: the
recovery path its author drew (stepResult.Success === false, or a fallback) is how the flow goes
on. Holding the fork because a higher-ranked path reads the answer that never came would stop it
from ever being taken. The paths are not evaluated — a negated read of a missing answer would come
out true — only set aside.
A fork with NO satisfied path is left alone: every path is unevaluable, the fork holds, and a
Retry of the failed Decision step can still route it. An answer below minConfidence is never set
aside; it holds, because its path might have been the one to take.
An exclusive fork's edges with each path that reads a FAILED decision counted as not taken, in every fork that has a satisfied path — so the satisfied one wins whatever its rank.
A failed decision call is a failed step, and a flow's failure handling is its outgoing paths: the recovery path its author drew (
stepResult.Success === false, or a fallback) is how the flow goes on. Holding the fork because a higher-ranked path reads the answer that never came would stop it from ever being taken. The paths are not evaluated — a negated read of a missing answer would come out true — only set aside.A fork with NO satisfied path is left alone: every path is unevaluable, the fork holds, and a Retry of the failed Decision step can still route it. An answer below
minConfidenceis never set aside; it holds, because its path might have been the one to take.