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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:25:20 UTC

C.16.Q:4.1c - Endpoint-first discipline

When the endpoint pattern or explicit endpoint source relation is already known, publish the evaluative form it defines directly. Keep qualityTermAscription(...) only when preserving the transitional ambiguity is itself informative. qualityTermAscription(...) is therefore a transitional characterization record, not a shadow endpoint source.

Typical direct endpoints are:

  • engineering -ility heads published as one Characteristic or one Q-Bundle,
  • selector-context uses published as an Objective headed by QS.UseValue unless overridden explicitly,
  • architecture-description uses published under the description-side evaluative head already selected by the viewpoint bundle,
  • explanatory-merit uses published under the explicit merit bundle when that bundle head is already known.