G.9:4.3 — Execution protocol (run‑time / selector‑adjacent)

Execution is one run under the pinned plan:

1. Validate CSLC references and pins. Validate the cited CSLC comparability and admissibility references, active pins, and witnesses; apply the eligibility or acceptance checks required by the pinned comparison and refuse or abstain on non-admissible operations. When the G.5 branch is current, use the exact planned TaskSignatureRef and the matching TaskMapRef when G.4 CAL gates apply; record the branch trace under its own result vocabulary. If a live A.21 gate consumes this check, cite its exact GateDecisionResult; cite a DecisionLog only when that optional audit or reuse record is needed. The profile application and its action consequence remain governed by A.21; do not create a G.9-local CSLC gate.

2. Run the comparison and any required selection. Apply the pinned comparator to the admissible comparison inputs and retain its lawful result shape in ParityReport. If a selector-facing result is required, apply G.5 under the plan’s exact task and conditional map refs and publish its declared outcome. An ordinary parity or benchmark report ends without G.5 when no selector result is needed.

   When parity is comparing bounded specialization, the report should echo the active specialization profiles or equivalent pins so readers can recover the work-measure threshold target, prior exposure, budget-to-threshold, post-threshold efficiency when relevant, transfer, retention, downside field, and any corridor-entry baseline or evidence note from the parity object itself rather than from later narrative explanation.

3. Record the comparability mapping when used. If UNM_id?, NormalizationMethodId[]?, or NormalizationMethodInstanceId[]? was declared, echo it in ParityReport or its explicit pins delta. Record the ids and any scoped notes required by the cited specification in the audit pins and SCR; cite the applicable PathId values.

4. Publish trace. Emit ParityReport with the exact ParityPlanRef, its BaselineBindingRef, conditional selector input refs, EvidenceGraph citations, and all active edition and policy-id pins, so the run can be checked and run again.

5. Emit telemetry hooks (optional, report‑only). When telemetry is produced, it is emitted as telemetry pins/events for refresh wiring (not as a silent change in dominance interpretation).