Ontological Parsimony

A.11 · Stable · Kernel parsimony and admission discipline pattern · Normative unless a section is explicitly informative · Part A - Kernel Architecture Cluster

About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Kernel parsimony and admission discipline pattern Status: Stable Normativity: Normative unless a section is explicitly informative

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.

Relations

A.11builds onU-kind Admission and Ontic Settlement

A.11builds onRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims

A.11builds onNeeded Relation Claim Derivation and Relation-Kind Admission

A.11builds onUniversal Core Principle

A.11builds onKinds, Intent and Extent, and Typed Reasoning

A.11builds onMint-or-Reuse Decision

A.11builds onLocal-First Unification Naming Protocol

A.11coordinates withOntic Candidate Detection and First-Use Disposition

A.11coordinates withOntic Description and Publication Discipline

A.11coordinates withUniversal Core Principle

A.11coordinates withKinds, Intent and Extent, and Typed Reasoning

A.11outline childDecision-Relevant Least Action and Operational Parsimony

A.11explicit referenceU-kind Admission and Ontic Settlement

A.11explicit referenceKinds, Intent and Extent, and Typed Reasoning

A.11explicit referenceNeeded Relation Claim Derivation and Relation-Kind Admission

A.11explicit referenceNaming Discipline for U-kind Names and SystemRoleKindDescription Labels

A.11explicit referenceMint-or-Reuse Decision

A.11explicit referenceLocal-First Unification Naming Protocol

A.11explicit referenceRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims

A.11explicit referenceUniversal Core Principle

A.11explicit referenceOntic Candidate Detection and First-Use Disposition

A.11explicit referenceOntic Description and Publication Discipline

Content

Use This When

Typical moments:

a new U-kind seems useful after E.24.UK;
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: the pattern either admits a new durable value with a boundary, or identifies the existing governed expression that already carries the claim.

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.

Problem Frame

FPF needs enough primitives to be useful, but every new primitive creates learning cost, bridge cost, and future repair cost. Ontological parsimony is not anti-growth. It is the rule that FPF adds a new kind only when composition, reuse, dependent-value settlement, and subject patterns cannot express the action-facing claim without material loss.

When source or draft wording proposes a candidate durable value in U.* form, treat that as an admission claim. Apply A.11 after E.24.UK recovers the governed object and before naming patterns choose a public label.

For a relation-kind candidate, first apply A.6.P. If the participants are exact but no current direct relation expresses the named receiving claim, apply A.6.RCD. Stop when it returns an existing exact predicate, a local compound claim, or subject-bounded or reusable predicate-definition content. A derived relation-kind candidate continues only when a named use needs stable occurrence semantics and supplies its proposed direct settlement; an irreducible primitive relation-kind candidate continues only under A.6.RCD disposition 4.

Problem

A useful project word, slot-position label, publication form, diagram element, mathematical lens, or repeated source term can start acting like a durable FPF kind before the governed object and subject pattern are recovered. The problem is to decide whether the candidate preserves an action-facing distinction that the best existing governed expression cannot carry, or should remain that expression or a local name.

Forces

Force	Tension
Expressive reach vs. kind inflation	FPF must name durable objects clearly, but each extra root kind increases learning, checking, and bridge cost.
Local usefulness vs. universal burden	A local project name may be helpful in one context, while a U-kind becomes a cross-corpus obligation.
Composition vs. material loss	Existing slots, relations, and patterns often express the claim, but some candidates preserve a distinction that composition would hide.
Reader clarity vs. ontology compactness	A plain label can help users, but a convenient label must not conceal a relation, slot position, publication form, or mathematical lens.
Growth vs. reopenability	FPF needs new primitives when problems demand them, but admitted values need reopen conditions when overlap or fuzziness appears.

Solution

Use four gates before admitting the new ontology addition. Apply every gate to the same exact candidate, receiving claim or use, and current facts. Record the best existing expression first; then state the exact loss, overlap discriminator, newly admissible claim or action, and nearest excluded case for that same use.

Gate	Test question	Pass condition
Composition	What is the best existing governed expression for this exact receiving claim or use?	Pass only when that expression loses a stated claim, boundary, or admissible use.
Non-redundancy	How far does the candidate overlap an existing governed value or relation, and what discriminates the remainder?	Pass only when the bounded remainder changes an admissible claim for the same use.
Action-facing contribution	Which exact claim or action becomes admissible because this addition exists?	Pass only when that contribution reaches the named use rather than supplying naming comfort or source prestige.
Sharp boundary	What is the one-sentence inclusion test, and which nearest case is excluded?	Pass only when both cases can be distinguished from stated facts without private author intent.

Use this compact record:

ParsimonyAdmissionRecord:
  Candidate:
  RecoveredGovernedObject:
  E24FamilySettlementDecisionRef: exact shared decision governed by E.24:4.0a
  ReceivingClaimOrUse:
  CurrentFactsRef:
  ExistingExpressionAttempt: best existing governed expression for that claim or use
  MaterialLossIfComposed: exact lost claim, boundary, or admissible use
  OverlapWithExistingValues: extent plus discriminator
  ActionFacingContribution: exact newly admissible claim or action
  BoundaryTest: inclusion test plus nearest excluded case
  Disposition:

Possible dispositions:

retain as a root U-kind;
retain as a dependent durable value under a root settlement;
retain as a local C.3 kind or typed claim;
express through an existing governed expression;
keep as source wording or a local name;
for a relation-kind candidate, stop at the exact [A.6.RCD](/generated/patterns/A.6.RCD) existing-predicate, local-compound, subject-bounded-law, or reusable-predicate-definition result;
retain a derived relation-kind candidate only with the required occurrence semantics and direct settlement; or
retain an irreducible primitive relation-kind candidate only when [A.6.RCD](/generated/patterns/A.6.RCD) disposition 4 passes.

Archetypal Grounding - Maintenance

Candidate claim	Parsimony result	Why
`CoolingPump` as a new root U-kind	First recover the project claim that distinguishes role classification, function, capability, component relation, or another governed expression. If that claim identifies an admitted `U.System` in an exact local cooling-circulator role, use the C.3 classification; otherwise return the missing discriminator. Add an assignment occurrence, capability, Method, or Work only when its own predicate is current.	The useful result follows the grounded project claim; the noun alone neither selects the role reading nor creates a universal kind.
`Actuator` or another transformer-like noun	Recover the system or holon that participates as transformer in a `U.Transformation`; admit a durable value only if `E.24.UK` shows irreducible action-facing gain.	The bearer of change and the transformation relation are already governed; the noun alone does not create a kind.
Provenance-chain wording	Try G.6 evidence-graph and provenance addressing first; admit a new durable value only if the direct evidence or provenance patterns cannot express the needed claim without material loss.	Parsimony tries subject patterns before minting a kernel addition.
`SmallPart` or similar vague size class	Reject or keep local.	The boundary depends on private scale expectations unless a direct measurement or classification pattern supplies a crisp rule.

A retained addition also needs a reopen condition. Reopen or lower the admission when usage collapses, overlap with an existing value is discovered, an existing governed expression becomes adequate, the boundary becomes fuzzy, or the name starts hiding that expression. This is maintenance discipline, not a fixed calendar ritual.

Bias-Annotation

A.11 corrects kind-inflation bias. A useful word, field name, record label, or diagram element can start behaving like a universal kind because it appears often, feels important, or has prestige in a source tradition. The repair is ontological: recover the governed object and try the best existing governed expression before admitting a new durable value.

It also corrects false-parsimony bias. A compact ontology is not achieved by refusing every new value. If composition hides a reviewable distinction or blocks an action-facing claim, parsimony admits the new value and states its boundary, overlap, and reopen condition.

Conformance Checklist

Check	Requirement
`CC-A11-1`	The candidate's governed object is recovered before parsimony is judged.
`CC-A11-2`	If the candidate uses `U.*` force, `E.24.UK` is applied before F.5, F.8, or F.18 naming.
`CC-A11-3`	The best existing governed expression is attempted by value. For a relation-kind candidate this includes the exact `A.6.P` / `A.6.RCD` disposition. A representation may supply evidence, but admission requires the stated irreducible claim, occurrence semantics, and boundary.
`CC-A11-4`	Material loss is stated as a lost claim, lost distinction, lost boundary, or lost admissible use, not as naming discomfort.
`CC-A11-5`	Strong overlap lowers or rejects the candidate unless the difference changes claims.
`CC-A11-6`	The final disposition is one of section 2's parallel outcomes and, for a relation-kind candidate, names the exact `A.6.RCD` result.

Common Anti-Patterns and How to Avoid Them

Slot label becomes kind. A system-role designation, transformation-participant label, source-maintenance position, carrier position, or boundary slot is renamed as if the label created a new universal kind; recover the admitted System, exact local system-role kind or direct relation, any separately obtaining assignment, and Work only when each is current.
Publication form becomes ontology. A card, record, view, dashboard, figure, or report title is treated as the governed object instead of the episteme, relation, or carrier it publishes.
Mathematical lens becomes object. A graph, tuple, algebra, metric, coordinate, or threshold is admitted as an ontology object without naming the EntityOfConcern and lens-use claim.
Local project name becomes kernel vocabulary. A useful project label is promoted to durable FPF vocabulary before composition and direct-pattern expression are tried.
Overlap is ignored. A candidate is admitted even though an existing pattern already carries the same claim with clearer boundaries.
Parsimony as refusal. A new value is rejected because "fewer kinds is better" even though existing composition loses a distinction users need to claim, compare, repair, stop, or rely on.

Consequences

Consequence	Benefit	Cost or boundary
Smaller durable vocabulary	FPF stays learnable and bridgeable across domains because already governed expressions do not become accidental U-kinds.	The parsimony record must show the best existing expression by value; hand-waving about simplicity is not enough.
Better U-kind admissions	New durable values enter only with material loss, non-redundancy, action-facing contribution, boundary test, and reopen condition.	Some attractive names remain local or dependent even when they are common in source traditions.
Clearer neighboring-pattern use	Readers know when to use E.24.UK, A.8, C.3, Part F naming, or a direct subject pattern.	The pattern does not choose the public name; it only decides whether durable ontology is warranted.

Rationale

Ontological parsimony preserves FPF's ability to handle many domains without turning every local distinction into a root object. The pattern follows the same discipline used by E.24.UK: recover the governed object first, then decide whether a new durable value is needed. Using an existing governed expression is a successful result, not a failure to mint a kind.

The practical criterion is not abstract minimalism. A candidate earns admission only when users gain a claim, comparison, repair, stop condition, reliance condition, or boundary they cannot recover by composition without material loss. That keeps parsimony tied to FPF's work-facing purpose rather than to a taste for small vocabularies.

SoTA-Echoing

Current ontology-engineering practice favors modularity, reuse, explicit competency questions, and controlled admission of new terms over unchecked class growth. A.11 adapts that practice to FPF: the admission question is not merely "can a class be defined?" but whether the candidate changes admissible claims, boundaries, or work-facing use inside the FPF pattern system.

Constructional-ontology and BORO-like source lines add a second discipline: identity, construction, dependency, and part-whole distinctions must be recovered before a convenient term becomes a kind. FPF keeps that source discipline without importing a classical top-level taxonomy as-is; U-kinds remain tied to accepted ontics, slot discipline, and action-facing pattern use.

Relations

Builds on: E.24.UK, A.6.P, A.6.RCD, A.8, C.3, F.8, F.18, and direct subject patterns.
Coordinates with: E.24.CD for candidate detection and E.24.PUB when a publication form or structural name created the admission claim.
Does not replace: universal-core testing in A.8, typed claim quantification in C.3, or naming discipline in Part F.

A.11:End

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)

#Ontological Parsimony

#About this pattern

#How to use this pattern

#Relations

#Content

#Use This When

#Problem Frame

#Problem

#Forces

#Solution

#Archetypal Grounding - Maintenance

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

#SoTA-Echoing

#Relations

#A.11:End

Ontological Parsimony

About this pattern

How to use this pattern

Relations

Content

Use This When

Problem Frame

Problem

Forces

Solution

Archetypal Grounding - Maintenance

Bias-Annotation

Conformance Checklist

Common Anti-Patterns and How to Avoid Them

Consequences

Rationale

SoTA-Echoing

Relations

A.11:End