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

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

E.17.1:12 - Relations

  • Builds on: C.2.1 for library and member-episteme identity; E.17.0 for exact P membership, reference resolution, singular use selection, and sole E/P view-membership rule; C.13 for explicit imported collections; A.22 for any separately selected organization; A.6.2-A.6.4 for optional episteme-construction histories; A.7, E.7, and E.10 for carrier, authoring, and naming discipline; E.24.PUB for publication; and C.29 for representation.
  • Constrains: E.17.0 consumers whenever they import a reusable family; an import narrows eligible references but neither selects one P for a use nor proves conformance.
  • Coordinates with: C.2.2a, A.16.0, E.17, E.17.2, E.18:5.12, F.9, F.9.1, and domain-specific families requiring stable reuse.
  • Protects: exact separation among catalogue triple <G_L, K_L, R_L>, catalogue episteme L, local declaration claim block, ordinary family designator, U.ViewpointRef, P designator, P, candidate/View E, any A.22 structure, form, carrier, publication occurrence, and C.29 representation.

E.17.1:12.1 - Resolvable annex references for thin bundles

An ordinary project family designator may be accompanied by references that resolve under the applicable source or reference scheme to exact annex assets. Each reference states its local role—such as lexical, bridge, movePublication, examples, optional sota, or optional pilotTrace. Neither the field spelling nor the role value creates a new reference kind, manifest entity, or typed annex asset. This keeps the declaration claim block thin while allowing A.16 move-publication notes, lexical material, Bridge material, and examples to remain explicit rather than folded into the core family claim.