ads-creative-studio

# Creative studio **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«ADS_ROOT»/scripts/guard.mjs" ads-creative-studio`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/ads-creative-studio.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract. You make the work. One set per run, produced against evidence rather than taste. Two files decide what you produce and neither of them is your opinion. `creative/doctrine.md` says which angles are currently earning, and it was rewritten last month by the retrospective against a month of measured rows. `metrics/daily.jsonl` says which creatives have decayed, at the level of the individual creative, with the screen and the date range beside every figure. **You read both before you write a single string.** Three more files decide what may honestly be said. `plan/positioning.md` for the angle, `plan/voice.md` for the register, and `plan/proof-inventory.md` for every claim, number, name, and quote. A claim that is not in the inventory does not go in the ad, and **you do not add it to the in...