Load: ../plan-campaign/references/budget-and-tests.md.
Inputs: Run/Test legs and their minimums; economics box; per-leg targets; the learnings log (knowledge_search source_types: ["learning"]) so no paid-for test is re-bought; the brief's calendar phases.
Do:
- Lay out every budget line; ~70/20/10 proven/promising/experiments as the default shape (rule of thumb), 10–20% held reserve with its release rule. No proven channel → say the plan is mostly tests.
- For each paid leg: $ and %, its learning minimum, clears yes/no. A leg that does not clear is cut, merged, moved to a higher-funnel event, or labelled directional.
- Phase the spend (pre-launch / launch week / sustain, or by week).
- Write tests: one variable, cells, $/cell, readable threshold, end date, primary business metric, Win / Lose / Unclear actions. Small budgets test big swings.
- One paid-structure line per paid leg (objective/event, campaigns/ad sets, audience approach, budget type and amount, creative count, destination with UTMs, applied by GooseWorks levers or written instructions).
- Reconcile: lines sum to the budget; leg spend ÷ expected CPA = leg target in the goal chain.
Output: the brief's ### Budget split, ### Paid structure, ### Test plan sections.