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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:40:18 UTC

A.10:6.2 - Common Anti-Patterns and How to Avoid Them

  • Carrier as truth. Recover the claim and direct source relation; authenticity or availability is not truth.
  • MethodDescription replaced by a plan or run trace. Recover the substantive generic method claims, including any intended effect, separately from a particular plan, dated Work, and actual bindings.
  • Generic result field. Name the domain result, the pattern that defines or tests it, and the distinct C.2.1 episteme.
  • Edge as fact. Establish the direct relation first; then let the graph represent or cite it.
  • Provenance as assurance or permission. Enter B.3, A.2.8.PER, A.21, or the pattern that defines or tests the additional claim only when that claim is live.
  • Citation as actual use. Ground the exact premise/reference/argument relation and any later Work claimed as such.
  • Full dossier by default. Collect only fields that decide the bounded use, consequence, contestability, and reopen condition.