Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:25:09 UTC

B.1.2:2 - Problem

Without B.1.2:

  1. Boundary by drawing. A box in a diagram is accepted as system delimitation.
  2. External relations become parts. Suppliers, grids, sensors, controllers, teachers, measuring instruments, or digital twins are placed inside the system because they interact with it.
  3. Functional and physical structures collapse. A resistor symbol, control function, chassis function, or service label is treated as a physical component by name alone.
  4. Whole-level characteristics lack grounding. Mass, capacity, reliability, safety, throughput, assurance, or agency-like characteristics are rolled up without saying which bearers, relations, and scales support the claim.
  5. Transformation becomes containment. A tool, teacher, actuator, script, or controller changes a holon and is then treated as its part or containing whole.
  6. Coordination record becomes ontology. One aggregate-shaped record silently creates systemhood, parts, boundary, crossings, allocation, evidence, and representation instead of pointing to independently governed facts.