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

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

F.18:1 - Context

Names are handles for use, not creators of ontology. A good name lets people talk about a governed value without smuggling in an extra system-role kind, assignment, capability, method, work, status, evidence, interface, or cross-context claim.

FPFCoreReferenceScheme is the by-value U.ReferenceScheme used to interpret current FPF Core Tech labels and relation names; a name under another scheme carries that scheme by value. Most naming work stays within one <ReferenceScheme, LocalSenseClaim> projection and needs no Bridge. If one named use must relate different projections, follow the later cross-projection branch in section 4.4.1. Shared spelling, another scheme, or a selected model-use structure alone creates no Bridge, use claim, reliance, governed-value identity, or U.BoundedContext.

F.18 supplies the naming discipline for Part F and for any FPF pattern that needs a durable public term. It coordinates with:

  • F.5 for type-name and system-role-kind-description label form;
  • F.8 for the prior decision that an expression should become a durable name rather than remain local, reused, or aliased;
  • F.9 for an actual sense Bridge between different <ReferenceScheme, LocalSenseClaim> projections;
  • F.13 for renames, aliases, splits, and merges;
  • F.14 for anti-explosion control;
  • F.17 only as a later public-row consumer whose current entry and result must accept the exact F.18 objects named below;
  • E.10.ROLE when bare claim-bearing role hides its object; A.6.5 and A.6.RSIR when relation, signature, interface, or slot wording hides the governed object; A.6.P.WMR when Work and Method boundary wording still hides the exact relation; and A.15.1 when a candidate performed-work name still lacks occurrence grounding.

The central subject is one F.18 naming settlement for one exact already-governed value. F.18 supplies the candidate comparison, selected Tech and Plain designations, declared naming use, and reopen conditions. The value’s direct pattern retains its kind, identity, obtaining, and other subject semantics.

Its complete claim graph records the selected designation expressions, exact local sense, covered and rejected alternatives, rationale, lineage, and reopen condition.