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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:40:20 UTC

C.2.LS:7 - Conformance Checklist

  • CC-C.2.LS-1 A language-state facet profile SHALL reference the patterns that define its facets rather than invent local unnamed factors.
  • CC-C.2.LS-2 C.2.LS MUST NOT redefine F or create a second formality progression.
  • CC-C.2.LS-3 Thresholds that matter for routing, reopening, or lexical repair SHALL be published on explicit facets.
  • CC-C.2.LS-4 Trajectory accounts that rely on facet profiles SHOULD reuse A.16 move kinds. Apply E.18 only to an independently selected TransformationFlowStructure; use E.18.2 when its mathematical description is needed.
  • CC-C.2.LS-5 Composite labels such as early, settled, or ready SHALL NOT stand in for the explicit facet bundle when those states matter operationally.
  • CC-C.2.LS-6 Composite readings, overlays, and route notes SHALL remain decomposable into named facets and MUST NOT behave as hidden master factors.
  • CC-C.2.LS-7 A profile bundle MUST NOT smuggle move rules, bridge rules, gate state, or downstream definitions and tests into what should remain a thin facet-profile record.