fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 58222–58243

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:45:20 UTC

C.20:0 - Use This When

Use this pattern when a team needs to decide whether an apparent field is one durable practice-and-knowledge whole rather than a convenient label or collection. Typical moments include:

  • comparing rival traditions within or across apparent disciplines without letting a shared label, Bridge, or comparison table merge them;
  • moving one practice across semantic localities while preserving the exact local meanings, direction, tolerated loss, and discipline boundaries;
  • judging whether an exact Method or method family actually belongs to a field assembly rather than being merely registered, used, cited, published, compared, or taught there;
  • keeping discipline continuity inspectable while its canon, standards, or accepted practices change, and identifying another whole when the reidentification rule fails;
  • deciding whether a research or engineering field has exact parts and a continuing identity;
  • deciding whether a theory, school, standard, or subdiscipline is actually a part;
  • using an applied, multidisciplinary, or transdisciplinary label without letting breadth wording create a kind or whole.

Primary EntityOfConcern. One exact U.Entity candidate being tested for recognition as U.Discipline. The candidate is recoverable before the classification result; calling it a candidate discipline does not make the result true.

First useful move. Name the exact candidate and two independently identified candidate parts: at least one making a knowledge-bearing contribution and at least one making a reusable-practice contribution. Then state why each direct part relation obtains and one whole-forming fact that couples the two contributions. Do this before letting the discipline name support a comparison, selector or dispatcher, health or maturity claim, transport, or edition decision. If those facts are unavailable, stop at the separately governed objects or collection.

What goes wrong if missed. A field name starts doing the work of a canon, method repertoire, institution, bridge, comparison policy, and maturity score at once. A card or graph can then manufacture parts, and changes to a journal, standard, method list, or dashboard can silently manufacture a new discipline. Cross-locality reuse can also look valid after local meanings, evidence lanes, or comparison rules have drifted.

What this buys. A practitioner can say what the discipline is made of, how the exact parts form one practice-and-knowledge whole, what remains the same through change, and which surrounding objects are merely used by discipline work. That makes comparison, transport, stewardship, and edition work inspectable without reducing the field to a document list or domain label.

Not this pattern when. Use domain or catalogue work for a subject-area label; use the effective ReferenceScheme, ClaimScope, and F.17 local-sense row for one local meaning; use F.9 only when a semantic relation is claimed between two exact F.17 SchemeSenseCell values from different semantic contexts and its predicate obtains; C.2.1 and its publication or source-use patterns for one theory, standard, canon item, or their exact episteme edition; C.3, C.2.1, and direct historical or provenance relations for a school, variant, lineage, or classification; A.3.1 and B.1.5 for a Method or composite Method; A.15.1 for dated Work; A.22 for a selected relation organization; A.19.CPM for an actual comparison; C.21 for field-health characteristics; and E.24.PUB for publication. Use C.20 when determining, explaining, or relying on whether one exact field-level candidate has the required construction and continuity. The result may be true, false, or unknown; when the constructive facts are unavailable, stop at a collection.