E.8:0.3 - Pattern Kind In Plain Terms

An FPF pattern supplies action- or judgement-guiding content for a recurring working situation. In ordinary phrases such as “use this pattern” and “apply this pattern”, the acting participant is the person or other capable system; the pattern is the guidance that participant uses.

Call the pattern content a U.MethodDescription only when it describes one independently admitted U.Method under A.3.2 and that distinction matters to the current claim. Keep the Method and its description episteme separate. A Solution can guide future action or help choose a Method without establishing that any dated Work has happened. The intended reader, an actual performer System, local system-role classification, assignment, capability, responsibility, authority, result, and Transformation remain separate whenever those claims are current.

When a pattern or worked case does assert dated U.Work, first recover every actual performer’s A.13 core: the admitted U.System, local agential kind and criterion, classification, same obtaining assignment, scope, working situation, window, and adequate core evidence; add a characteristic profile only when its own receiving use consumes it. Then independently admit the Work under A.15.1 from its performance history, enacted Method, time, and containing System. Add F.6 afterward only when the pattern also needs precise assignment-bound attribution through that same assignment. A short practitioner sentence may omit identifiers unused by its receiving claim only when every relation the claim consumes remains recoverable.

Pattern application is ordinary shorthand for user-side use: a user or another capable system recognizes the situation and uses the pattern’s Solution to choose the next action or judgement. The pattern body is description-side guidance. Assert a performer, assignment, dated U.Work, result, or U.Transformation only when independently established and material to the receiving claim; a Conformance Checklist checks the authored description and evidenced use but does not replace the Solution.

The pattern’s main job is constructive action or judgement guidance. In the opening Problem frame and Solution, state the primary EntityOfConcern, first admissible move, first useful result or practical delta, and only the boundaries that change that move. Error prevention, auditability, conformance evidence, citations, and architecture rationale remain secondary. Repeat another source’s distinction only when it adds a local action, case, evidence value, or recognition needed on first reading. State what this pattern governs; do not surround it with an unbounded catalogue of other things.

Name an FPF object by its known kind and state the relation the sentence actually uses. For a neighbouring pattern, state its concrete contribution and cite the PatternID; identify an exact episteme, ClaimGraph, edition, or relation assertion only when that identity changes the receiving use. Put detailed discovery in its dedicated carriers, including README, ToC, E.11, and keep compact pattern relations late in Relations. Do not repeat the same boundary or reference family in small prose variants.

Use E.8 to keep the pattern’s positive subject and action guidance first. Apply F.19 once to each changed natural span as the common precise-plain-language pass. Its connected reading owns language-general semantic completeness and contribution, coordination and foregrounding repair, kind and loss preservation, and local revalidation after wording changes. These facets form one connected F.19 reading, not separate E.8 checks.

For FPF authoring, E.8 adds the pattern-specific question: can the intended reader still recognize this pattern’s EntityOfConcern, working situation, first action or judgement, first useful result, and action-changing boundary before optional modeling and assurance? A cold reader must recover that path from the pattern body; F.19 governs the sentence-level recovery. Do not copy its method, regression table, or result boundary into a local authoring profile.

If the F.19 reading leaves an FPF value unresolved, take the exact E.10, E.10.ARCH, E.10.ROLE, A.6.F, F.18, or subject-pattern route and state that source’s concrete contribution. Ordinary PatternID citation and “use this pattern” wording remain ordinary; use an identity-bearing MethodDescription or dated Work claim only when the selected route requires it. Keep development and release evidence outside practitioner guidance unless rewritten as the user’s action or boundary. When an action-adjacent pattern classifies wording or another semio-facing object, connect that classification to the reader’s current action. State the admissible use now and any independently grounded boundary that changes that use. Route any other genuinely live claim to the FPF pattern that defines or constrains it.

Semio-Echoing is admissible only for one grounded wording-use overread that changes the reader’s action or boundary. Keep the pattern’s own EntityOfConcern, positive move, and result primary. Use a thin cue to the exact subject pattern only when its contribution is needed; do not add a generic counterreading catalogue.