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

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 08:00:10 UTC

A.3:3 - Problem

Legacy phrasing (“actor / process / blueprint”) causes recurrent failures:

  1. Self‑magic in an actor-side claim: “the system configures itself” is used as if it already supplied a performer, role assignment, method, work occurrence, causal relation, and evidence.
  2. Plan = event: blueprint/algorithm reported as if execution happened.
  3. Capability or Method = Work: having a capability or a Method is taken to establish that Work occurred.
  4. Episteme as doer: documents/models treated as actors.
  5. Occurrence-description leak: a method, plan, log, ticket, carrier, or evidence item is treated as the dated Work occurrence, while the assertion fails to designate the actual performer assignment, enacted Method, extent, affected referent, and direct relations. A.2, A.7, A.10 and A.15.1 supply these distinctions, but A.3 must give the canonical quartet that authors can apply consistently.