Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

A.19.CPM:7 - Conformance Checklist

Apply the declaration checks to a CPM publication and the application checks to a use, together with the applicable A.6.1 checks and, for CHR membership, A.19.CHR:4.3. Replay always requires the application and its local bindings. Neighboring Work, evidence-use, reliance, currentness and result-episteme checks apply only when the account asserts those objects or the receiving use consumes them:

Check IdRequirement (normative)Notes (didactic and evidence)
CC-A19CPM-0Mechanism declaration completeness. One U.Mechanism episteme, its comparison-operation-family EntityOfConcernRef, effective reference scheme, operation-local argument/result declarations, OperationAlgebra, LawSet, AdmissibilityConditions, Applicability, and optional SignatureManifest are recoverable.Applications, bindings and neighboring claims are checked separately under §4.1.
CC‑A19CPM‑1Single governing pattern. The CPM intension is governed here (A.19.CPM:4.1); other descriptions cite this section rather than restating the kernel law.Prevents near-duplicate comparison semantics from drifting.
CC‑A19CPM‑2Suite stage alignment. Compare is the canonical stage‑op for CHR stage compare; ordering and optionality are taken only from A.19.CHR:4.5.Never infer order from mechanisms[].
CC‑A19CPM‑3SlotKind discipline. SlotKind tokens follow the suite lexicon (A.19.CHR:4.2.1).No SlotKind drift across specializations and wiring.
CC‑A19CPM‑4Comparator admissibility gate. ComparatorSpecSlot ∈ CGSpecSlot.ComparatorSet is enforced (fail-closed otherwise).Admissibility is declared, not improvised.
CC‑A19CPM‑5Scale admissibility. Any numeric operations implied by the comparator are admissible under CGSpecSlot.SCP and CSLC-admissible.“Weighted sum” etc must be explicitly admissible.
CC‑A19CPM‑6Set‑valued semantics. Outputs remain set‑valued; no silent scalarization or totalization is introduced.Incomparability and ties are first‑class outcomes.
CC‑A19CPM‑7Tri‑state admissibility (fail‑closed). `CompareEligibility(…) → {passdegrade
CC‑A19CPM‑8MinimalEvidence defaulting is explicit. If MinimalEvidenceSlot? is absent, the effective evidence policy is CGSpecSlot.MinimalEvidence.Avoid “implicit evidence policy.”
CC‑A19CPM‑9Gate and guard separation + lexeme discipline. CPM does not publish GateDecision nor DecisionLog; mechanism predicates use …Eligibility (not reserved gate …Guard).Aligns with suite obligations (gate_decision_separation, guard_lexeme_reservations).
CC-A19CPM-10Bridge and reference-plane discipline. A comparison that relies on a semantic relation between two F.17 SchemeSenseCell values cites an obtaining F.9 Bridge under a satisfied BridgePredicateProfile and a separate C.2.1 bounded-use claim; a plane-only crossing cites the ReferencePlane relation and policy; both are stated when both facts are current.CL is optional. CPM supplies no default assurance penalty, fold, or R_eff; a local R_eff is admissible only for a named assurance claim under its declared domain model and calculation. These neighboring facts are not CPM declaration content.
CC-A19CPM-11Replay basis completeness. The Compare or CompareEligibility application and its bound profile, comparator, U.ClaimScope, selected A.2.6 context-slice, optional A.19 predicate, reference-scheme and plane, evaluation-window and policy arguments are recoverable, together with the corresponding returned ComparisonResultSlot or GuardDecision value or its explicit absence.If asserted or consumed, independently recover dated comparison Work through the A.13 core and A.15.1 admission in §4.1, evidence use under A.2.4, currentness under G.11 and a result episteme under C.2.1. Use A.10 when the bounded source-to-use account must remain replayable. These facts remain outside the output value.
CC-A19CPM-12Planned-filling separation. On a P2W path, an A.15.2 baseline selects intended editions and policies; A.15.3 typed filling applies only to independently declared positions. Compare applications carry their effective argument and result bindings.A dated comparison Work and any relied-on A.10 provenance remain separately established.
CC-A19CPM-13No implicit UNM. When comparability depends on normalization, CPM uses the explicit upstream directed result and preservation/loss basis. A class-level comparison also passes its query/operation conditions under A.19.UNM; a reference or equal normalized numeral alone is insufficient. Unsupported comparisons follow abstain or the declared narrower degrade use.Keeps compare-on-invariants explicit.
CC-A19CPM-14Comparison-scope completeness. Every Compare application binds one profile pair, U.ClaimScope, selected A.2.6 context slices, optional A.19 predicate, effective reference scheme and plane, and explicit evaluation point or interval.No generic context input, optional model-use structure, or label supplies these values.
CC-A19CPM-15Outcome separation. ComparisonResultSlot contains only the by-value set of relation or poset tokens; GuardDecision remains the separate eligibility value, and abstention fabricates no output token.Comparator, scope, plane, window, evidence, provenance, currentness, result episteme, and selection remain separate.
CC-A19CPM-16No generic result relation. The A.6.1 operation application binds the output; C.2.1 governs a durable result episteme when needed; subject patterns govern any other result relation.CPM mints no universal comparison-result or work-result link.