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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:15:17 UTC

C.2.LS:16 - Profile Publication Package Discipline

C.2.LS:16.1 - Minimal publishable profile package

A publishable U.LanguageStateFacetProfile should normally carry:

  • the declared facet refs for AE, CD, LanguageStateAnchoringMode, and LanguageStateRepresentationFactorBundle;
  • any threshold refs that substantively affect routing, repair, bridge interpretation, or review load;
  • the local relation to F when readers might otherwise treat F as a surrogate;
  • any omission note when a facet is intentionally unpublished, unknown, or locally irrelevant.

One-line publication is admissible only if the facet definitions and tests remain legible.

C.2.LS:16.2 - Partial-profile rule

A partial profile is admissible only when omission is explicit. Publishing AE and CD while deferring LanguageStateAnchoringMode is acceptable; silently omitting it and then speaking in scalar prose such as “early” or “ready” is not.

If only one facet is published, either explain why the others are not included in the current note or point to the note where they are already published.

C.2.LS:16.3 - Overlay discipline

Local overlays such as “explicit-but-open”, “trace-heavy”, or “operator-tight” are admissible only when they dock to explicit facet refs. Overlays remain secondary to the declared profile and must not replace the facet bundle.