A.19.CHR:7.2 - Planned baseline checks

CC‑A67CHR‑10 (Planned baseline exists). Every P2W path slice using the suite has an A.15.2 WorkPlan baseline with the selected suite and member declaration editions.

CC‑A67CHR‑10a (Typed filling has its governor). Use a CHRMechanismSuiteSlotFillingsPlanItem only when A.15.3 applies to an independently declared operation argument or relation position. Cite that declaration and position; a suite field is insufficient.

CC‑A67CHR‑11 (Plan and enactment). Planned references and values establish no actual binding, launch value, execution witness or gate decision.

CC‑A67CHR‑11a (Use anchors). Recover the described entity, bounded context, CG-frame, path slice, publication scope, reference plane when current, and explicit time rule needed for the declared use.

CC‑A67CHR‑11b (Expected guards). Expected guard pins belong to {USM.CompareGuard, USM.LaunchGuard} and name the responsible gate when later event aggregation requires it.

CC‑A67CHR‑11c (Spec baseline). The baseline cites CN-Spec and CG-Spec and their selected editions. Cite the independently declared position separately when either reference is also used as a typed planned argument filling.

CC‑A67CHR‑12 (Exact edition resolution). Each used declaration and operation has one governing edition. Multiple applicable editions require a selection condition before use; a source list or implicit latest does not resolve them.

CC‑A67CHR‑13 (Applicable crossing references). Expected crossings cite only the relations, policies and bundle anchors their governing rules require; the baseline embeds no CL/Φ tables.

CC‑A67CHR‑14 (Audit traceability). Later Work audit can cite the exact WorkPlan and baseline locator and distinguish actual bindings or deviations from planned values.