C.24:4.2 - Bounded scout or probe cycle
When the action remains fixed but an unresolved route condition could change the continuation, first use adequate interface documentation, existing observations or provider information. Select a bounded scout only when its attainable answer can change the warranted continuation enough to justify its burden, within the applicable budget and permission. State what observation would retain, revise or reject the route before planning that scout. Its actual performance can support a CheckpointReturn; an unfamiliar route alone does not require probing.
- If another probe could still change which option survives the
OptionSet, the budget remains a C.11 probe budget and planning returns there. - If changed live facts or domain-Method limits could change an A.15.7 action, return there instead.
- If a prescribed action loses its applicable prescription, return to the domain Method before further route planning.
- If the action or option remains fixed and only route shape or rollout order is uncertain, the probe uses enactment budget and its checkpoint belongs here.
commitTrigger states the condition for considering a checkpoint decision to end route probing and adopt an identified CallPlan for the fixed action. Name the proposed plan and the work it schedules in recommendedNextAction or in the accompanying explanation. When the trigger holds, the responsible planner considers that transition using the probe evidence, residual budget, and any required safety or assurance result; the planner may adopt the plan, require a further bounded probe, or stop. Satisfying the trigger alone does not make that decision.
Adopting the plan settles which route to use. Permission to perform its calls remains subject to the applicable work-entry conditions, and actual performance is separate U.Work. Where an autonomy budget governs the route, use the checkpoint decision and guard or override path in E.16-S1.A; the trigger grants no wider budget or scope.