Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:20:09 UTC

C.17:4.4 - ConstraintFit: which must-criteria hold?

ConstraintFit reports satisfaction of the declared must-constraints under their predicates and source epistemes. Use E.5, D.1-D.5, or a service-acceptance pattern only when it supplies the actual predicate or source for the current must-criterion. A ratio such as passed declared must-constraints / all declared must-constraints is allowed when the set and any criticality weights are explicit.

A failing must-constraint makes the bearer ineligible for the affected use unless the receiving constraint or decision pattern recognizes an independently obtaining exception or waiver effect. A waiver speech act alone does not change eligibility. If no pattern defines the needed effect, return the missing relation rather than treating communication as authorization.