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 15:41:27 UTC · snapshot created 2026-10-03 15:43:46 UTC · last check 2026-10-03 15:55:10 UTC

E.17.2:2 - Problem

How can engineers reuse a compact family of these four concern-bearing viewpoints while keeping all of the following distinct:

  • the exact holon described by a candidate episteme;
  • the exact viewpoint episteme and its exact target kind or, only in the triggered structured branch, its selected convention structure;
  • the candidate episteme and any dependent U.View membership;
  • a viewpoint selected for one describing use;
  • the Methods, transformations, selected structures, local system-role kinds, assignments, modules, and interfaces mentioned in the claims;
  • any viewing construction, evaluation, cross-view relation, publication occurrence, form, representation, or carrier?

Without that separation, a label such as functional view can stand indiscriminately for a concern convention, a diagram, a query output, a report section, or a claim about a system. The next engineering action then relies on the wrong object.