E.18.1:4.1a - Conditional development-loop relation-selection extension
Open this didactic extension only when cheap generation, open-ended search, or evolutionary-engineering work has produced many variants before the project has a stable problem, comparison basis, selected set, work entry, or currentness relation. Apply the unchanged P2W core to the one question that changes the next action. The four rows below are discriminators, not a second relation-selection map; use the single map in Relations only after the question is stated.
If the current question is still problem formulation or opportunity, return first to C.22.2 to accept or revise the ProblemCard@Context and its carried claim. That is an upstream return, not another downstream P2W result.
| Source cue | Ask this concrete question | Continue or stop |
|---|---|---|
| “We generated many variants.” | Which variants are actually retained, and under which descriptor or front? | Carry the returned archive/front value. If no retained-set relation is current, keep only the candidate-set cue. |
| “This is the best set.” | Is the current claim comparison, selector application, local choice, selected-set result declaration, or actual publication? | Split those claims. Apply only the branch being asserted; a score or front supplies none of the others. |
| “The candidate is ready.” | Is the team planning work, checking entry readiness, reporting a dated U.Work occurrence, claiming a gate or permission result, or asserting acceptance for one named use? | Name one question and use the Relations map once. For acceptance, name the predicate and its participants; stop if ready or accepted is the only basis. |
| “We trust the generator.” | Does the sentence name an autonomy declaration or boundary—what the generator may do or spend, and when it must stop—or is it about evidence, assurance-sensitive confidence, permitted action, or merely a project label? | For a declared autonomy limit, apply E.16 and carry its exact declaration or boundary result; that result supplies no evidence, assurance, or permission. Otherwise apply A.10, B.3, or A.2.8.PER only to the one claim actually made. If the phrase is only a label, retain it and make no action claim. |
Cheap variant generation shifts effort toward problem production, characterization, archive stewardship, fair comparison, explicit choice, autonomy boundaries, evidence, assurance, performed work, effect measurement, currentness, and repair. P2W preserves the accepted problem-side claim while one of those relations becomes current; an archive, front, selected set, confidence phrase, or choice rule supplies neither an A.2.8.PER permission result nor performed work. Source wording such as trust budget, problem factory, solution factory, or factory of factories remains a project label until the evidence, assurance, autonomy, work-organization, or other direct relation is named.