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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:20:15 UTC

B.4.1:7 - Conformance Checklist

  • CC-B.4.1-1 Observe output SHALL NOT be forced directly into AnomalyStatement when articulation threshold is not yet met.
  • CC-B.4.1-2 A routed cue set SHALL name its candidateRouteSet.
  • CC-B.4.1-3 When route selection occurs, routeDecision, selectedRoute, and routeRationale SHALL be explicit.
  • CC-B.4.1-4 publicationFaceRefs MAY be named, but route-bearing form and publication face SHALL NOT be collapsed.
  • CC-B.4.1-5 RoutedCueSet SHALL NOT be treated as establishing a late endpoint result.
  • CC-B.4.1-6 When a specialization-sensitive route is kept live, the route package SHALL name the declared task family or utility target, the current budget window if known, the missing discriminator still needed, and the downstream subject pattern that would become applicable if the discriminator and that pattern’s other entry conditions are satisfied.