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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:15:11 UTC

C.2.5:7 - Conformance Checklist

  • CC-C.2.5-1 Closure SHALL be declared independently from F and AE when it matters for routing, docking, or reopening.
  • CC-C.2.5-2 Reopen/backoff moves SHALL cite the prior closure state they are relaxing.
  • CC-C.2.5-3 Strong-closure states SHOULD name the guard, governingPatternRef, or authoritySourceRef that makes the closure binding.
  • CC-C.2.5-4 A closure drop SHALL NOT silently preserve an endpoint-use claim when the supporting route or publication form no longer supports it.