Library.Reference:3 - Why general Methods belong in Core

FPF Core contains both common conceptual distinctions and developed transdisciplinary Methods. Its Kernel is the subset that defines universal meta-concepts and the rules for their meanings and relations. Core also explains how to investigate a question, construct and combine Methods, compare arrangements, qualify claims, make decisions and continue development. The Kernel is not the whole of Core.

The placement question turns on what an operation requires. Constructing a Method from interacting contributions, comparing its performance and provision, or deciding which questions a checklist must answer can apply across fields without importing one field’s substantive mechanism. These general constructions belong with their shared conditions in Core. Repeated domain copies add a duty to keep the same general construction consistent.

For example, FPF C.32.MWA.PP constructs and compares complete performance and provision arrangements. FPF A.15.8.MS configures the methodological support that actual work needs. FPF C.41 and its connected patterns distinguish selecting checklist questions, making their reusable expression, fitting an occasion, obtaining grounded answers, reconciling shared uses and qualifying the checking means. These remain several Methods with different results, rather than one compulsory checklist process. FPF E.8.ML explains the construction of a pattern language for connected Methods.

Wide applicability alone does not justify Core placement. Mathematical Modeling constructs correspondences, transformations and mathematical consequences under mathematical premises. Research Method Practice reconstructs practice and investigates competing accounts under inquiry-specific evidence conditions. Organization Change Engineering constructs contribution, information, assignment and authority arrangements in an organization whose work continues. The common idea of improving a method does not teach those specialized operations.

The architecture therefore keeps a general construction once and gives its specialized realization an explicit supplier. The test is whether the full operation and its conditions survive a change of subject, and what domain knowledge still has to be supplied. An abstract object, a broad title or use by many professions cannot settle that test. FPF E.4.PFAD compares the actual contributions and their organization; FPF E.4.CM distinguishes an already explained connection from a missing reusable Method.