E.11.PUA:10 - Rationale

FPF patterns supply action- or judgement-guiding content for recurring working situations. Some selected Solution sections describe methods; others define, constrain, test, or guide a judgement without doing so. Establish formal U.MethodDescription membership under A.3.2 only when the episteme’s EntityOfConcern is an admitted Method, at least one claim concerns that Method as a way of doing, and that distinction changes the claim. The missing middle is neither discovery nor recommendation: use one selected conditional Solution to identify the first result with its own identity and basis that answers the current question, or stop when its basis is missing.

Separating ordinary semantic checking from conditional record materialization protects both usability and rigor. A conversation can be sufficient for a bounded reversible question. Another person’s later use, an audit, an automated use, or an expensive decision can demand addressable support. The same ontology serves both profiles; only the reliance changes the recording granularity.

The first-result boundary prevents proxy completion. A plan, note, simulation, or assessment may be valuable and may be the result at the current pattern-use position. It cannot stand for a later physical, clinical, organizational, or learned change. Stop where the current basis supports value, then continue under the pattern that defines, constrains, or tests the next result or relation.