G.10:8 - Conformance checklist (CC‑G10)
This pattern inherits order/illumination, evidence, and bridge/penalty legality from the cited governing patterns (not restated here). Shipping‑specific requirements:
| ID | Statement | Verification notes (conceptual) |
|---|---|---|
| CC‑G10‑CoreRef | The pattern satisfies the effective G.Core obligations declared by G.10:4.1 (after profile/set/pin‑set expansion under Nil‑elision). | Check that the linkage manifest is present and that the expanded obligations are not contradicted. |
| CC‑G10.1 (Notation‑independent). | The pack MUST NOT rely on any specific file syntax; cards/tables are conceptual; tool serialisations are informative only. | Look for format‑free conceptual fields; any serialisation is explicitly non‑normative. |
| CC‑G10.2 (Pack parity pins). | If QD/OEE fields are present, pin DescriptorMapRef.edition, DistanceDefRef.edition, and (OEE) TransferRulesRef.edition; when a shipped field actually consumes a C.21 DHC coordinate, carry every active field of that coordinate’s DHCReplayBasis instead of a generic method-spec or metric-edition pin. Include CharacteristicSpaceRef (+ CharacteristicSpaceRef.edition when it affects partitioning reproducibility); for QD archive semantics also pin EmitterPolicyRef and InsertionPolicyRef. | Verify the corresponding G.10:Ext.* block is present and the pins appear in AuditPins and (when relevant) in telemetry pins. |
| CC‑G10.3 (Telemetry discipline). | Any illumination increase or archive edit SHALL log PathSliceId, the active policy‑id, the active editions of the pinned …Ref fields (incl. OEE TransferRulesRef.edition), and the active EmitterPolicyRef/InsertionPolicyRef when applicable. | Verify emitted telemetry is PathSlice‑keyed and carries the required pins; ensure causes are recorded using canonical trigger kinds (alias labels optional only). |
| CC‑G10.4 (UTS publication & twins). | Shipped heads use UTS Tech/Plain twins under the delegated publication rule. A shipped cross-context semantic-use claim cites its obtaining relation, separate bounded-use proposition and matching reliance; calibration summaries keep their evidence role. Kind and plane claims retain their own governors. | Verify the published names and exact relation/use evidence; a visible CL or policy pin alone is insufficient. |
| CC‑G10.5 (MOO surfaced in shipping). | For every declared selector set-result or archive published, the pack SHALL list the applicable generation/parity method and mechanism ids (e.g., QD EmitterPolicyRef/InsertionPolicyRef, parity harness ids, method refs where the method definition is generative) and the active policy‑id(s) in SCR‑visible bindings and telemetry pins (ids only; governing-definition delegating). | Verify MOOManifestId is present when outcomes are intended for downstream use and does not redefine semantics. |
| CC‑G10.6 (Pack completeness as a citation surface). | The pack cites all included upstream artefacts by id/ref and exposes the required pins (AuditPins, UTS/Path pins, CrossingBundleIds when required). | Verify all present payload artefacts have ids and the pins needed to cite/replay them. |
| CC‑G10.7 (CrossingBundle exposure). | For each GateCrossing relevant to shipped artefacts, the pack exposes the relevant CrossingBundleIds (or records that no such crossings exist) per delegated crossing visibility discipline, and shipping fails fast on missing/non‑conformant crossing bundles when required. | Verify crossing bundle presence/absence is honest and aligned with the shipped artefacts’ declared crossings. |
| CC‑G10.8 (Baseline binding is explicit when used). | If the shipped pack claims a planned baseline, PlanItemRefs := ⟨WorkPlanRef, planLocalContentLocator⟩[] are present (exact WorkPlan plus plan-local content; no execution logs). | Verify the baseline resolves inside the cited WorkPlan; item and row designators have no independent identity, and decision records or execution logs do not replace the plan. |
| CC‑G10.9 (Extension‑scoped pin declaration). | If QD/OEE/interop fields are present, the corresponding GPatternExtension block is present and its required pins/editions/policies are recorded in AuditPins and in emitted telemetry pins when those pins affect refreshability. | Verify conditional extension pins are not silently omitted when the mode is used. |
| CC‑G10.10 (Derived tradition-view shipping). | If the visible shipped surface or shortlisted source is one derived tradition view such as TraditionFront or TraditionArchive, the pack MUST publish the declared sourceSetFamily, keep basePaletteRef=SoTAPaletteDescriptionId recoverable, and carry the derivation basis (derivedViewKind, declared Q, or reachability/coverage rule id) with enough explicitness that the visible surface cannot be mistaken for the default palette semantics. | Verify derived tradition views are shipped as derived views, not as silent redefinitions of the base palette. |