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

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:10:20 UTC

A.22:2 - Problem

FPF needs a selected-structure EntityOfConcern that is usable across domain ontologies, mathematical formalisms, architecture notations, and publication forms. Working projects often notice that “the structure” is doing real work:

  • dependencies repeat across cases;
  • a method or work description hides an invariant relation;
  • a model compresses a trace by preserving one relation class and losing others;
  • a diagram shows an arrangement but is mistaken for the arrangement itself;
  • a mathematical lens exposes preserved structure but is then overread as ontology;
  • an architecture discussion needs selected structure over a holon before it can describe architecture.

How can FPF let a practitioner name structure as an EntityOfConcern while preserving the distinction between:

  • selected structure and the source-description relation, source-use relation, evidence relation, lens output, simulation, generated representation, or declared substrate from which it was inferred or declared;
  • structure and a Description episteme or view of that structure;
  • structure and a publication face, diagram, table, graph, or publication form;
  • structure and mathematical-lens application;
  • structure and another FPF claim kind whose definition or test remains in the cited pattern;
  • structure in general and architecture-specific structure selected by C.30.