C.24:7 - Conformance Checklist

1. Every result states exactly one grounded action basis: an applicable domain-prescribed action with its Method, prescription and conditions; an A.15.7 decision episteme; or a C.11 choose-now ChoiceResult. A WorkPlan alone supplies no permission or authority, and a prescribed action needs no fictional decision or ongoing Work.
2. Every planned step names an A.3.1-admitted Method that realizes or supports the fixed action. The action basis fixes the action or option; selecting it does not establish Method identity. Route-description refs remain separate and optional.
3. The plan records time, compute, cost, and risk ceilings plus stop or replan conditions.
4. C.18 candidates or front material and C.19 live-pool treatment may inform the action basis but do not admit Methods; C.24 owns only planning and replanning results.
5. A scale branch first cites one actual C.19.1 probe result, then any selected comparison or Scale-Audit result; a BLP-waiver remains separate from evidence.
6. Every vendor-bound ATC.CallRouteDescription identifies source scheme, exact edition, intended use, and selected Method; an arbitrary profile, adapter, or Bridge cannot substitute.
7. Each current policy or constraint ref resolves to its actual C.19, C.19.1, B.3, or domain-defined object; a plan with no such branch remains valid.
8. A CheckpointReturn states tested Methods, evidence, burned and residual budget, next action, and commit trigger.
9. Actual call claims retain dated Work, performer, Method, interval, plan, budget delta, and G.6 trace refs; the admitted System performs and records the Work.
10. A causal action-use branch uses the current C.28 question, support-component, and support-result contract and grants no downstream authority.
11. The ordinary quick path remains readable without ontology or assurance apparatus.