Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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:25:09 UTC

F.5:9 - Consequences

Good consequences:

  • durable names become shorter because the ontology stays at the right object;
  • local system-role-kind names stay usable without becoming assignment, capability, Method, or evidence claims;
  • description names no longer collapse into the kinds they describe;
  • U-kind names are easier to bridge because their comparison evidence remains explicit; and
  • For an E.10 repair that uncovers a durable naming issue, use F.5 or F.18 instead of ad hoc word substitution.

Costs:

  • authors recover the object and meaning source before naming;
  • some familiar source labels cannot become FPF Tech designations;
  • durable public names may need F.18 and F.17, while actual cross-local relations may need C.3.3 or F.9 even when a local label looks obvious; and
  • source text that uses role for status, evidence, access, participation, or relation position needs ontological recovery, not suffix editing.

Reopen F.5 when U-kind neutrality, SystemRole or SystemRoleKindDescription morphology, the Tech-Plain relation, lineage, or durable cross-local naming boundaries change. Reopen a neighboring pattern when the dispute is about the named object itself.