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

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

A.16.1:7 - Conformance Checklist

  • CC-A.16.1-1 A cue pack SHALL NOT be presented as a claim, characteristic, method, work occurrence, or route-decision record.
  • CC-A.16.1-2 A cue pack SHALL make cueNucleus explicit.
  • CC-A.16.1-3 When preservation depends on privileged grounding, primaryWitnessRef or primaryAnchor SHALL be explicit.
  • CC-A.16.1-4 laneCandidates and routeCandidateHints MAY be published early, but selectedRoute, routeRationale, and route-selection status SHALL NOT be smuggled into the cue pack.
  • CC-A.16.1-5 If route-candidate hints are not yet nameable, publication is still admissible only when preservationRationale and grounding make the preservation need explicit.
  • CC-A.16.1-6 Language-state, anchoring, and representation-factor details MAY be referenced; use C.2.LS for the facet profile, C.2.4 for articulation explicitness (AE), C.2.6 for anchoring mode, C.2.5 for closure degree, and C.2.7 for representation factors.
  • CC-A.16.1-7 A cue pack SHALL NOT claim that an endpoint test passed or that a stronger use is admitted; use the applicable endpoint pattern to test and publish that later result.