C.24:0.2 - What this buys

• one small, tool-neutral plan that cites the accepted action basis;
• visible budgets, stop conditions, and replan triggers before calls are made;
• one replayable call-trace reference after Work occurs; and
• one bounded checkpoint when more route probing is justified but commitment is not.

Primary working object. One ATC.CallPlan : U.WorkPlan. Each step selects a U.Method. A route description may help locate or constrain that Method, but remains a separate U.MethodDescription. Actual calls are dated U.Work and remain outside this planning result.

First useful move. Identify the applicable domain prescription, A.15.7 decision or C.11 choose-now result that fixes the action. Fill that one branch of actionBasis. Then write the ordered Method refs, budget, stop or replan condition, and next planned action. Add route-description refs only where the route cannot be understood without them.

Not this pattern when. Use C.11 while fixed-option choice is unresolved, C.19 while treatment of a live pool is unresolved, G.5 when the current task is selector-facing result declaration, A.15.5 for work-entry readiness, and A.15.1 when the question is what Work actually occurred or which Method it enacted.