Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:15:17 UTC
C.25:7 - Conformance Checklist
CC-C.25-1 If an engineering quality claim is intended as one measurement characteristic, the publisher SHALL bind it to one named U.Characteristic with one declared scale.
CC-C.25-2 If the claim requires multiple measures, scope slots, mechanism slots, status slots, or qualification windows, the publisher SHALL use Q-Bundle-shaped ClaimGraph content rather than an undeclared scalar surrogate.
CC-C.25-3ClaimScope and WorkScopeSHALL remain USM set-valued scope objects; they MUST NOT be treated as ordinal or numeric quality levels.
CC-C.25-4 Mechanism or status slots MUST NOT be conflated with Measures[CHR].
CC-C.25-5 Any scalar comparison or thresholding inside a Q-Bundle SHALL apply only to declared CHR measures, not to scope slots.
CC-C.25-6 When cross-context comparison is current, the publisher SHALL align the exact bundle heads or slots, resolve the two exact F.17 local senses, and, when their <ReferenceScheme, LocalSenseClaim> projections differ and the comparison needs semantic correspondence, test the direct F.9 Bridge predicate and state a separate bounded-use claim only if that Bridge obtains. The comparison and its reliance MUST NOT change any Q-Bundle slot; ordinary reliance uses A.10, while B.3 opens only when an actual named assurance claim is current.
CC-C.25-7 A materialized Q-Bundle SHALL be recoverable as content of one exact C.2.1 episteme with one independently identified QualityBearer as EntityOfConcern and one effective ReferenceScheme. A gate, publication, comparison, proxy, or roll-up MUST NOT cite a field list as though it were an independently identified bundle object.