E.11.PUA:4.0 - Cheap first screen before formal work identity

Start with five ordinary values: the working subject, the practical question, the selected pattern’s Solution, the first useful result or blocker, and the stop or return. For a bounded reversible use, those values are sufficient when the result and boundary are truthful.

When following a pattern exposes a costly, infeasible or apparently unhelpful demand, use C.11.DUA to examine what that work can change and repair the continuation. Follow the selected method through its first useful completion, including any prescribed fields or records. Keep the result and its useful basis; retain a reason or limitation when the current decision or a later recipient needs it. An inactive inquiry adds no omission account. This route is conditional on the demand being in question.

An FPF pattern supplies action- or judgement-guiding content; a person or another capable system uses it. The ordinary instructions “use this pattern” and “apply this pattern” are harmless shorthand. Only when the selected Solution actually describes a Method and that distinction changes the claim, use A.3.1 to identify the admitted U.Method and A.3.2 to test U.MethodDescription membership of the pattern episteme. Name a System, system-role classification, assignment, plan, dated Work, result, or U.Transformation only when that object is part of the current claim. Assignment never substitutes for the acting System, Work, authority, or responsibility.

When those identities do matter, keep them separate: the pattern episteme is not the acting System or Work; a selected or project-tailored Method is not automatically a WorkPlan; intended work is not performed Work; a result, evidence for it, and a later use are different values. This conditional distinction introduces no universal workflow, causal chain, production relation, TFS, or record requirement.

Before Method selection, distinguish the missing operation. Use C.39 when a sufficiently clear local result lacks an adequate obtaining explanation; it can finish with one explained candidate or the precise unresolved contribution. Use C.40 when usable material needs variation, examination and warranted continuation, whether or not its ultimate contribution is settled; its C.40:4.3 entry adds problem construction and target-tested transfer when those are needed together. A sufficient existing Method or result exits directly, and ordinary use of a selected pattern requires neither search.

If the working question is still represented only by a pre-method-selection TaskSignature, use that signature to constrain method search; do not treat it as the task, plan, or Work occurrence. Use OEE or NQD to retain Method or architecture candidates before selection, and use G.5 to declare a selected-set result. For publication, use E.17 for a source-backed face and return to source and E.24.PUB for the occurrence, form, carrier, audience, bounded use, and availability. Use A.3.1 to identify a selected Method and A.15 for planning and Work. Open these distinctions only when candidate retention, selection, result declaration, publication, planning, or performed Work is current.