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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:40:09 UTC

E.17.1:2 - Problem

When recurring viewpoint families lack a stable catalogue:

  1. Each domain invents local viewpoint families. Similar families reappear under slightly different labels, but no stable catalogue U.Episteme records whether the underlying viewpoints are actually the same.
  2. Viewpoint identity drifts. A family called functional, capability, or operational may differ only lexically, or may differ semantically, but there is no disciplined place to tell which is which.
  3. MultiViewDescribing cannot reuse a family cleanly. Each describing use that needs the family must restate it locally instead of importing an existing bundle.
  4. Reusable viewpoint-library practice remains external. FPF lacks a native place where reusable viewpoint families can be expressed as reviewable catalogue content without importing a standard’s ontology.
  5. Reader-facing labels leak into semantics. Authors reuse the same name for viewpoints, views, publication faces, or folders, and the boundary between EntityOfConcern and Description episteme becomes unclear.