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

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

C.2.3:7 - Conformance Checklist

  • CC-F-1 Every normative U.Episteme SHALL declare exactly one U.Formality value, either a default anchor or a local sub-anchor explicitly docked to one.
  • CC-F-2 F SHALL be treated as an ordinal characteristic; arithmetic over F values is invalid.
  • CC-F-3 Higher F SHALL mean greater or equal strictness of expression, not greater truth, trust, or scope.
  • CC-F-4 Contexts MUST NOT publish alternative “formality modes” or “tiers” as surrogates for F.
  • CC-F-5 Local sub-anchors SHALL preserve the global ordering and the parent anchor meaning.
  • CC-F-6 For a composite episteme assessed as one expressed claim or argument, its F SHALL be bounded by its least-formal essential content or inference on the declared compositional support path. Identify that assessed bearer and support relation. This expression-wide cap does not extend automatically to external evidence cited as warrant.
  • CC-F-7 Implementations MUST NOT average F values numerically.
  • CC-F-8 Changes in G, R, or CL SHALL NOT change F unless the expression form itself changes.
  • CC-F-9 Cross-context transport SHALL preserve the attributed F when formal content is preserved. If the receiving rewrite changes claim content, EntityOfConcern, or the effective reference scheme under C.2.1, the result is a new episteme with its own F.
  • CC-F-10 Translation loss, bridge loss and plane crossings SHALL retain their actual receiving-use limitations. Evaluate any assurance effect under its governing model; do not hide it as an F change when the expressed content is preserved.
  • CC-F-11 Assigned F values SHALL be justifiable by observable content such as explicit predicates, executable semantics, or machine-checked proofs.
  • CC-F-12 Declaring a tool or notation SHALL NOT by itself justify a higher F unless the content satisfies the target anchor semantics.
  • CC-F-13 Status labels such as Draft, Approved, or Published MUST NOT substitute for F.
  • CC-F-14 A context that uses F in gates or policies SHALL write those thresholds explicitly.
  • CC-F-15 Language-state facets such as articulation or closure MUST NOT be hidden as pseudo-levels of F.