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

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:50:10 UTC

A.6.F:9 - Consequences

BenefitCost or trade-off
Function-like prose remains usable without minting U.Function.Claim-bearing uses must name the exact object or claim and subject pattern; additional relation, declaration, assertion, specification, view, or representation objects appear only for a named use.
Functional architecture becomes a normal architecture-by-structure-kind case.C.30 or C.30.ASV may be needed when the phrase carries an architecture claim.
Capability, method, Work, system-role kind, assignment, participation, functioning, responsibility, mathematical, quality, module, and interface claims stay separable.One familiar word may require several independently established objects or claims when several readings are current.
C.29, C.25, C.16, A.15, C.30, and A.6.M govern only the claims that belong to them.A conforming use stops once the exact object or claim, subject pattern, and remaining action are clear instead of opening all possible subject patterns.