G.12:6 — Conformance checklist (CC‑G12, normative)

Preface node heading:g-12-6-conformance-checklist-cc-g12-normative:60132

Content

CC IDRequirementVerification notes
CC‑G12‑CoreRefThe pattern satisfies the effective G.Core obligations declared by GCoreLinkageManifest (G.12) (profiles/sets/deltas expanded per G.Core:4.2).Evidence: the manifest is present; required pins/defaults/triggers are accounted for; no local restatement overrides core owners.
CC‑G12.1DHC slot typing (C.21‑grounded). Every published dashboard value is indexed by a C.21‑authored DHCSlotId (typed DHC slot: CharacteristicId + scale/unit/polarity + reference plane binding + lane discipline) and is scoped by an explicit TargetSlice + Γ_time.Evidence: row/series references DHCSlotId and pins ReferencePlane and Γ_time (or a series WindowSpec that yields row Γ_time).
CC‑G12.2Edition discipline (no drift). Every published time‑series value carries DHCMethodRef.edition and any other definition‑pins actually used to obtain it (e.g., DescriptorMapRef.edition, DistanceDefRef.edition, UNM_id, NormalizationMethodInstanceId[], ComparatorSetRef.edition?). No free‑text versioning.Check that .edition appears only on …Ref; check presence of all definition pins used by the pipeline; extension pins appear only when their extension blocks are present.
CC‑G12.3Contract citation for numeric operations (no shadow specs; no illicit arithmetic). Any numeric operation in the dashboard pipeline is legal only under explicit CG‑Spec and CN‑Spec pins (e.g., SCPRef.edition, MinimalEvidenceRef.edition, ΓFoldRef.edition? when used), and any normalization is explicit (UNM_id + NormalizationMethodInstanceId[] etc). Ordinal/categorical slots remain compare‑only (no illicit arithmetic).Check that operations cite pinned owners; reject “normalize, then compare” without explicit UNM pins; reject arithmetic over ordinal slots unless an owner‑declared lawful mapping exists.
CC‑G12.4Set‑returning selection is preserved. If the dashboard consumes selection/portfolio outputs, it MUST preserve set‑return semantics and MUST publish the resolved DominanceRegime and PortfolioMode by citing the single owners (via G.Core.DefaultOwnershipIndex) rather than inventing local defaults. Any promotion of illumination/telemetry into dominance MUST cite the owner policy (typically CAL) and be auditable via evidence paths.Check for set/portfolio outputs; check that any scalar headline is view‑only; check citations to owner defaults/policies.
CC‑G12.5UTS publication discipline. DHCSeries@Context and its rows (and any published slices) are published as UTS artefacts with Tech/Plain twins and stable identifiers; deprecations/edition bumps follow the canonical UTS discipline.Check stable ids + twin labels; check that publication does not smuggle “gate decisions” as authoritative artefacts.
CC‑G12.6Bridge/plane routing is explicit when used. If a series crosses contexts or planes, the rows MUST cite the Bridge/PlaneMap routing (BridgeId[], CL/CL^k/CL^plane, Φ/Ψ/Φ_plane policy‑ids, PlaneMapRef.edition?) and respect penalty routing to R_eff only (semantics routed via G.Core).Check presence of crossing pins when contexts/planes differ; check that any loss is expressed via R‑lane impact only.
CC‑G12.7Telemetry sufficiency for slice‑scoped RSCR. Emitted dashboard telemetry pins MUST (i) use canonical RSCRTriggerKindId, (ii) include scope (PathSliceId[] or PatternScopeId) and the touched …Ref.edition/policy/window pins, and (iii) block publication when required pins are missing. Each published row is evidence‑citable by PathSliceId[] under explicit Γ_time.Check: no free‑text causes; payload includes path/window/editions/policies; missing pins block publish; row has PathSliceId[] and Γ_time.
CC‑G12.8Extension gating. If any extension‑owned fields/pins appear, the corresponding G.12:Ext.* module is present and satisfied.E.g., QD pins require G.12:Ext.QDTelemetry; maturity panel requires G.12:Ext.MaturityLadderPanel; SoTA palette hooks require G.12:Ext.SoTAPalette; pack inclusion requires G.12:Ext.PackInclusion.