C.11:4.4 - Reroute as soon as the question stops being local choice
Use C.11 while the question remains: from this current OptionSet, what should the DecisionSubject choose, and is another probe worth its cost before commitment?
Reroute immediately when the question changes:
- If the current rows are labels or fragments and the hard question is how several complete ways could obtain the same result, leave this pattern and work in
C.38first. - If a way to obtain the result still needs explanation, use
C.39. If usable material needs feasible variation and examination, useC.40. UseC.18when the question concerns the generation account or archive/front stewardship. - If the options already exist but the question is how broadly to keep exploring or exploiting the candidate pool, leave this pattern and work in
C.19, where the next useful output is one explicit pool-policy result rather than one localChoiceResult. - If one option is already chosen and the question is how to sequence, budget, or enact that choice, leave this pattern and work in
C.24, where the next useful output is one enactment-facing call plan orCheckpointReturn. - If the question has shifted from deciding to declaring or naming selector-facing selected-set content, leave this pattern and work in
G.5. Its next useful output may be aShortlistorRankedShortlistwhen alternatives remain for later choice, aJointUseSetwhen every named member is included for one bounded use, a narrowed handoff, abstain, or escalation. None is one more localChoiceResult. If that result already exists and the current question is presentation or availability to an audience, useE.17for the source-backed publication face and return to source andE.24.PUBfor the publication occurrence and availability.
ProbeBudget stays here while it means the epistemic or deliberative budget for one more probe before choice and while that probe can still change which option survives or whether the current set should be rejected. When the same word now means execution budget, call budget, enactment budget, or execution-path scouting after one choice result already exists, the question has moved to C.24.
ValueOfInformation and ValueOfComputation also stay theory-side here as comparative criteria while the question is still local choice among the current options. If one more probe could still change which option survives or whether the current set should be rejected, stay in C.11. If the choice result is already fixed and those criteria now govern only execution-path sequencing, call-plan ordering, or enactment of the chosen option, the question has crossed to C.24. C.19 and C.24 may consume the criteria, but they do not become the doctrine authorities for them.
Outside this pattern remain candidate generation, pool-wide exploration policy, selector-facing set-result declaration, publication availability, and execution planning.