run-paid-campaigns

What you get

• On the first run, an account baseline — structure (ad sets under the learning floor, overlapping audiences), spend concentration by concept, creative age and mix, tracking state — which seeds the first moves (consolidation, rotation, fixes). references/baseline-audit.md.
• Weekly moves proposal (budgets in the marketer's currency) — in the report shape (references/proposal-and-log.md): In short (what a customer may cost, data window, what is and isn't visible), checks and pacing vs ceiling, since last time (each earlier move: done or not, and worked / didn't work / too early / can't tell, measured against the baseline stored when it was staged), then every move this week — scale / pause / hold / rotate / launch / graduate / fix / instructions — each with its evidence, confidence, what should happen, how it's applied and a check date. Near-threshold calls carry both readings and a trip-wire. Shape: references/proposal-and-log.md.
• What to do: approve in three bundles — approval links for Meta budget changes, swaps and launches (one approval each; GO LIVE typed for increases and live swaps), one sentence the marketer says for pauses, and written instructions for everything outside GooseWorks' reach. With the marketer's own ads connector, a card per change, each applied on its own named yes.
• Change log in the server's campaign-harness format — ads/campaigns/<slug>/state.md and decisions.md — so every approval, decline and pause is recorded and results trace back to decisions.
• A run record for next week (references/run-memory.md): the per-ad scorecard (top 10 by spend plus all others, with the trend since last run), every money move with its baseline recipe and verdict, and the open moves with their review dates — saved to the brand so the next run, the performance read and the replan all start from what happened.

Before you start