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

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:30:15 UTC

F.4:2 - Problem

Without this pattern:

  1. Description and kind collapse. The description is treated as the local system-role kind.
  2. Description and classification collapse. A card is treated as proof that one candidate satisfies the kind criterion.
  3. Description and assignment collapse. A kind name or card is treated as proof that one system has an assignment.
  4. Description and capability collapse. A kind name is treated as evidence that a system can do the Work.
  5. Description and Method collapse. Kind criteria become a hidden procedure or MethodDescription.
  6. Description and performed Work collapse. A card is treated as evidence that Work happened.
  7. Status and episteme uses become system roles. Publications, standards, datasets, claims, and statuses acquire fake system-role classifications because they matter to reasoning.
  8. Relation positions become system roles. Participant meanings, declaration slots, interface places, and representation positions are mistaken for system-role kinds.
  9. Same-spelled kinds collapse or fragment. Shared spelling is treated as proof of one kind, or a changed practice or source as proof of two, without comparing the candidate domains, operative membership conditions, member/non-member boundaries, and continuity rules.