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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:40:20 UTC

A.19.SPR:6 - Conformance checks

CheckRequirement
CC-A19SPR-1The final sentence names the exact item and what is claimed or valued, or explicitly keeps the wording ordinary, quoted, navigation-only, narrowed, or blocked.
CC-A19SPR-2The direct rule or criterion is recoverable whenever the claim is not understandable or usable without it.
CC-A19SPR-3A predicate appears only when the direct pattern defines or needs one; relations, assertions, results, decisions, and record fields keep their own forms.
CC-A19SPR-4An allowed-use or blocked-inference clause appears only when it changes the receiving action or prevents a likely harmful conclusion.
CC-A19SPR-5A time window, expiry rule, or recheck condition appears when the value can change during the intended use.
CC-A19SPR-6Source, evidence, assurance, publication, assignment state, work entry, gates, decisions, release or admission, and project records use the patterns or records that define or test those exact claims.
CC-A19SPR-7Source and publication patterns are not used as a general home for evidence, assurance, gate, Work, temporal, mathematical-lens, or project status.
CC-A19SPR-8A retained technical field names its item, possible values, and rule; it adds use, time, evidence, and blocked-inference fields only under their triggers.
CC-A19SPR-9A cold reader can say what the sentence is about, what it claims, and what to do or check next. Type-correct but opaque wording fails.
CC-A19SPR-10Corpus repair classifies each use; it never performs a blind global replacement of posture, state, status, or readiness.