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

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

A.6.RSIR:4.4 - Reduced-use source labels

Reduced-use labels are allowed. They are not failures. A source label remains reduced-use when it helps readers find or recognize the case but does not carry FPF-governed content.

Examples:

  • “API role” can remain a quoted source phrase while the branch is selected with E.10.ROLE. The repaired claim may be an API description, an exact provider system-role assignment, a declaration or representation position, a promise-content episteme under A.2.3, an independently obtaining commitment under A.2.8, PromiseContentUse, a delivery or acceptance relation, another named direct relation, or an interface specification.
  • “parameter” can remain ordinary prose while a complete SlotSpec is named only for a current reusable relation declaration, an operation ArgumentDeclaration or ResultDeclaration and any exact application binding stay under A.6.1, and a method-call, formula, or other representation position stays under C.29 or its exact representation pattern.
  • “function” can remain ordinary engineering language when no architecture, capability, method, work, mathematical, quality, or module claim depends on it.