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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:20:08 UTC

A.11:0 - Use This When

Use this pattern when FPF work proposes a new U-kind, core relation, dependent durable value, or public structural name and the current question is whether existing ontology can express the claim without the proposed durable ontology addition.

Typical moments:

  • a new U-kind seems useful after E.24.UK recovers the candidate object;
  • a proposed root kind may actually be a dependent value, slot, relation, record, publication form, lens, local frame, or C.3 U.Kind;
  • two candidates overlap strongly;
  • a name is convenient but the ontology may already be expressible through existing patterns.

Primary EntityOfConcern. The EntityOfConcern is the parsimony claim for one candidate ontology addition.

First useful move. Recover the candidate with E.24.UK or the subject pattern, then find the best current FPF expression for the exact receiving claim or use.

In this pattern, an existing governed expression is an admitted kind or dependent value, slot, current relation, record, publication form, lens, local frame, or direct-pattern claim whose direct owner defines its use.

What goes wrong if missed. FPF grows duplicate kinds for claims already carried by governed expressions. Later patterns then argue over words instead of recovering the EntityOfConcern, exact relation or slot, and admissible claim.

What this buys. A small ontology can still express rich project situations: A.11 either identifies the existing governed expression that carries the claim or supplies a positive parsimony finding, with a boundary, for the candidate’s complete admission test.

Not this pattern when. The current question is only a local display name, publication title, naming taste, or ordinary glossary cleanup. Use the relevant Part F naming pattern unless the name is being asked to carry durable ontology.