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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:10:10 UTC

E.17.2:6 - Consequences

GainCost or boundary
One project can make four familiar engineering concern positions reusable across its holons after exact local bindings exist.Materializing L, four exact P editions, and four reference resolutions is real work; equal labels do not create cross-project reuse.
Viewpoint episteme, its exact target kind or conditionally selected convention structure, view episteme, and described holon remain distinct.Authors recover P’s truthful EntityOfConcern—its exact admitted target kind by default, or S only in the triggered structured branch—and exact H as EntityOfConcern(E).
Directly authored and generated descriptions use one conformance rule.Query or rendering provenance cannot substitute for conformance.
Cross-view engineering claims keep their direct semantics.A package or diagram cannot provide realization, allocation, or consistency by appearance.
Publication can evolve independently of the engineering viewpoints.Publication forms and carriers need their own direct relations when they affect work.

Reopen the TEVB template when its four positions no longer give a small useful engineering concern family for routine holon description. Reopen one materialized local instance when a bound P’s exact target criterion or conformance rules change, or when a candidate concern cannot be expressed without changing a local binding. Author another local family instead when the concern is orthogonal rather than a replacement for the four.