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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:15:10 UTC

C.21:9 - Conformance Checklist

CheckPassing condition
CC-C.21-1The discipline, intended use, one exact Characteristic, Scale, ClaimScope, comparison or observation basis, and time stance are recoverable.
CC-C.21-2ClaimScope is authoritative. A TargetSliceRef appears only when consumed and its exact relation to the scope is stated.
CC-C.21-3A minimal readable claim may stop without a definition set, EvidenceGraph, registry, dashboard, or publication apparatus.
CC-C.21-4Every persisted, compared, aggregated, or published coordinate carries the active DHC replay basis; no generic “metric edition” substitutes for an exact object.
CC-C.21-5Characteristic, Scale, Unit, polarity or target rule, and legal operations are coherent. Ordinals are not averaged and Units are not mixed.
CC-C.21-6Direct comparison uses C.16’s compatible-semantics branch. A comparison that relies on a cross-local semantic relation keeps the obtaining F.9 relation, its separate bounded-use claim, observed loss, and current reliance distinct as specified in section 4.2.
CC-C.21-7Formal recognition and actual adoption or convergence are separate Characteristics; neither rank proves health or SoTA.
CC-C.21-8EvidenceUnitResolution, ClaimsPerArtifact, and SupportAnchorsPerClaim are separate; their constructions and Units are not interchanged.
CC-C.21-9Entropy and concentration are separate, with opposite directions explicit; any transformation and receiving Scale are declared.
CC-C.21-10Measurement definition, exact Method, MethodDescription, model, calibration, Work, result, result episteme, series episteme, dashboard representation, publication occurrence, form, and carrier remain distinct where present.
CC-C.21-11Freshness, evidence reliance, assurance, acceptance, public naming, and refresh machinery appear only when a named receiver consumes them.
CC-C.21-12Unknown inputs remain unknown under the receiving method; missing inputs are not coerced to zero or to a health verdict.
CC-C.21-13Engineering-grade extension readings cite the direct pattern and rule and do not become evidence, assurance, gate, release, Work, or project authority.