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

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 09:10:20 UTC

F.4:9 - Consequences

Benefits.

  • Descriptions stay short enough for practice while preserving the ontology.
  • Part F naming and Bridge patterns can cite descriptions without inheriting classification, assignment, capability, Method, Work, evidence, or status claims.
  • Episteme-use relations stay direct and do not become a parallel system-role ontology.
  • Method and Work checks may cite the description without treating it as Work evidence.

Costs.

  • Former “role-or-status template” material must move to F.10, A.2.4, B.3, A.10, E.17, G.6, or another direct relation.
  • A stronger claim may require several neighboring patterns instead of one overloaded card.
  • Public, Core-facing, or durable cross-local names require F.18.