E.10:0.2c.15 - pattern, generic FPF-side object wording, locus, row, target

Pattern is not a free synonym for regularity. If the intended object is an FPF pattern, write FPF pattern or name the pattern and the definition, constraint, test or method being used. If it is not an FPF pattern, do not write recovered FPF construction as the final value. Choose one recovered value by sentence function: episteme, view, publication, publication form, generic publication face, declared MVPK face, PublicationUnit, carrier relation, front-end relation, project-side FPF kind and reference named by value, document with named source-basis, evidence-basis, architecture-basis, or review-basis relation or use, review target, obtaining direct relation and actual participants, receiver-needed relation occurrence, reusable RelationSignature and A.6.5 SlotSpec values, claim-bearing episteme with any current participant designations, C.29 representation element and explicit correspondence, C.11 ChoiceResult, C.11 decision record, A.6.A action invitation, A.15 U.WorkPlan, one A.15.1 dated Work occurrence admitted under U.Work or a separate episteme about it, U.Method, U.MethodDescription, A.20 constraint or adjudication decision record, A.21 GateDecisionResult, an optional A.21 DecisionLog, independently established evidence-use relation recovered through A.10, typed evidence record, B.3 assurance or engineering-justification record, or typed status record whose FPF status pattern is named.

Avoid generic FPF-side object wording, generic named-target wording, locus, row, and host when they hide kind. Use them only when the kind is literally a table row, document with named source-basis relation or use, file carrying FPF pattern text, or review target and the sentence does not need a narrower FPF kind. For FPF-facing wording that carries a claim being made, direct relation, admissible use, or remaining reader use, these are candidate recoveries, not a group kind: FPF pattern, pattern section, accepted DRR, FPF publication, FPF view, record kind with its defining rule, obtaining direct relation and actual participants, receiver-needed relation occurrence, claim-bearing episteme, reusable A.6.5 declaration, or C.29 representation and explicit correspondence. Choose one by sentence function and keep the different objects separate.