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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 07:55:10 UTC

A.3.2:9.1 - Quick use cards

  • Claims first. The claim-bearing episteme can be U.MethodDescription; its exact U.Method, C.29 representation, publication occurrence, publication form, and U.PresentationCarrier remain distinct.
  • Executable is still not a run. Runs are Work individuals admitted under U.Work only when A.15.1 grounds their occurrences.
  • Representation is not enough. Read what the code, proof, solver file, procedure, diagram, or workflow actually asserts and name its subject. Only the claim-bearing episteme can pass A.3.2 membership; C.29 keeps the representation correspondence.
  • Mechanism needs its declaration. Use A.6.1 when operation algebra, laws, admissibility, or applicability is current; keep transport, audit, realization, evaluation, and evidence-use relations under their direct patterns.
  • Math needs its own claim. Use A.6.0 and C.29 when formal substrate or mathematical-lens use is current.
  • No ordered-action overread. Use C.2.P.DR when declarative representations are overread as ordered action structures.