A.19.ULSAM:7 - Conformance Checklist (normative)

ID	Requirement
CC‑A19ULSAM‑0	Mechanism declaration completeness: §4.1 MUST supply the A.6.1 operation-local arguments/results, application predicates, identity/extent rules, laws and admissibility/applicability conditions. SlotIndex projects those declarations.
CC‑A19ULSAM‑1	Single governing pattern: the ULSAM declaration is governed by §4.1; a use cites it rather than inferring semantics from a copied summary.
CC‑A19ULSAM‑2	No hidden aggregation: any Γ‑fold MUST be explicit as `ULSAM.Fold_Γ` (no folding hidden inside `Score/Compare/Select`, including inside `USCM/CPM/SelectorMechanism`).
CC‑A19ULSAM‑3	Scale-lawfulness: a conformant ULSAM fold MUST be CSLC-lawful and admissible under `CGSpecSlot.SCP`. Ordinal arithmetic is forbidden unless explicitly allowed by the relevant CSLC fragment.
CC‑A19ULSAM‑4	Γ‑fold admissibility: a conformant ULSAM publication MUST ensure `GammaFoldSlot` resolves to `CGSpecSlot.Γ_fold` or an explicitly pinned override (CAL policy). “Implementation default fold” is non-conformant.
CC‑A19ULSAM‑5	Evidence gating: a conformant ULSAM publication MUST guard folding via `FoldEligibility_Γ` with `GuardDecision ∈ {pass
CC‑A19ULSAM‑6	SlotKind discipline: SlotKind tokens used in the ULSAM intension MUST come from the CHR SlotKind Lexicon (`A.19.CHR:4.2.1`). New SlotKinds require lexicon extension first.
CC‑A19ULSAM‑7	Audit surface: Audit MUST record `CNSpecRef.edition`, `CGSpecRef.edition`, and the effective `ΓFoldRef`; and MUST record `MinimalEvidenceRef` when overridden (else cite `CGSpecSlot.MinimalEvidence`).
CC‑A19ULSAM‑8	Contributor accountability: when `ContributorSetSlot?` is produced, it SHOULD be recorded (or referenced by stable id) as an explanation surface for what contributed after admissibility/evidence gating.
CC‑A19ULSAM‑9	P2W separation: the A.15.2 baseline MUST select the intended fold/evidence policies and editions. A.15.3 typed filling applies only to independently declared positions. Actual Fold_Γ bindings MUST obtain under §4.1 and remain distinct from planned values and their Audit representation.
CC‑A19ULSAM‑10	Gate/guard separation: ULSAM MUST NOT embed GateDecision/GateLog or publish/telemetry operations in the `fold_Γ?` stage; admissibility is via `FoldEligibility_Γ` (tri‑state) and run‑time observability via `Audit` pins only.
CC‑A19ULSAM‑11	No implicit UNM: ULSAM MUST NOT silently normalize/rescale to force comparability. When normalized inputs are required, cite the upstream directed result and preservation/loss basis in Audit. A class-level fold also needs compatibility, partial-availability and receiving-query recovery under A.19.UNM; invoking UNM alone supplies none of them.