C.11:4.2.4 - Closure rule over the current OptionSet

C.11:4.2.4 - Closure rule over the current `OptionSet`

The comparison may close as choose now only when all of the following are true together:

the current OptionSet is stable enough that no further options are being invented for this comparison;
the current comparison basis is explicit enough to state why one option survives or why one tie-set remains;
no still-feasible next probe is expected to change the survivor relation with enough expected value to justify its cost;
the record still concerns local choice rather than pool policy, selector-result declaration, publication availability, or enactment.

The comparison may close as reject current set only when all of the following are true together:

the current OptionSet is explicit and stable enough to reject as the present choice set;
the current comparison basis is explicit enough to show why no member survives under the present basis;
no still-feasible next probe is expected to rescue one member with enough expected value to justify its cost;
the result is still one local choice conclusion rather than one disguised pool-policy, selector-result declaration, publication-availability, or enactment result.

Assess the probe conditions above from the current basis and any live inquiry alternative. They are conditions of a warranted choice, not a requirement to produce a separate account of omitted checking.

The comparison should close as probe again only when all of the following are true together:

one next probe is named by value;
that probe fits the remaining ProbeBudget;
that probe is expected to repair one named comparison defect;
that repaired defect could still change which option survives, whether the current set should be rejected, or whether the question should reroute.

The comparison should close as reroute when the record shows that the decision question has changed:

to C.38 when labels or fragments must first become complete-enough ways of obtaining the same result;
to C.39 when a way to obtain the result still needs explanation;
to C.40 when usable material needs feasible variation and examination;
to C.18 when the question concerns the generation account or archive/front stewardship;
to C.19 when the question is now how broadly to keep exploring or exploiting one candidate pool;
to C.24 when one choice result already exists and the next task is now sequencing, enactment, or execution-path probe work;
to G.5 when the next task is declaring or naming selector-facing selected-set content; when that result already exists, use E.17 for its source-backed publication face and return to source and E.24.PUB for the publication occurrence and audience availability.

If none of those closure conditions can yet be satisfied, the record is still unfinished. It is not rescued by richer terminology alone.