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

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 05:30:50 UTC

C.2.LS:14 - Authoring and Review Guidance

C.2.LS:14.1 - For authors

When publishing a language-state facet profile:

  1. start from the local authoring problem rather than from a memorized progression;
  2. name the facet refs explicitly;
  3. add threshold refs only when a threshold changes routing, repair, or another operative decision;
  4. avoid global labels such as “mature”, “raw”, or “ready” unless the profile decomposition is already visible.

C.2.LS:14.2 - For assurance readers

An assurance reader should ask:

  • is any facet silently replaced by F?
  • is a threshold published on an explicit facet rather than on a poetic surrogate?
  • do route or reopen claims actually match the published facet bundle?
  • are profile notes genuinely informative, or are they smuggling definitions or tests from elsewhere?

C.2.LS:14.3 - For integrators

Integrators should preserve profile references rather than rephrasing them into local slang. A local alias is acceptable only if the underlying facet docking remains explicit and stable.