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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:25:20 UTC

A.13:2 - Problem

Treating agency as an intrinsic property or a mere label hides different questions:

  1. Episteme-as-Actor: When “the specification decided to update the system” hides the actor, use A.12 to identify the proposed acting entity. A precise agency claim needs that entity admitted as a System under A.1, distinct from the specification under A.7.
  2. Type Inflation: Introducing a root agent kind alongside U.System and U.Episteme would violate Ontological Parsimony (C-5). The same System may qualify for an agential system-role kind and receive an assignment in one working situation but not another. The agency claim states its scope and window separately; a root type cannot express these differences.
  3. Unsupported Claims: A label such as “agent” supplies neither the local kind criterion and obtaining assignment nor evidence for a claimed autonomy profile. Those claims need their own support under A.10.
  4. The Binary Trap: “Agent/not-agent” alone does not distinguish a thermostat’s feedback, a cruise-control system’s prediction and a strategic robotic swarm’s self-learning capabilities.