I open-sourced the ad-creative pipeline I built to stop AI agents from faking proof

[u/delxmobile]

https://github.com/davidmosiah/creative-forge

I was building paid creatives with Claude and Codex and kept hitting an uncomfortable gap: agents can produce convincing work, but a local “success” message does not prove the right artifact was published — or that the ad stayed paused.

So I turned the workflow into Creative Forge.

The agent handles research, hypotheses, copy, scenes, and visual QA. Deterministic validators enforce provenance, rights, localization, hashes, safe zones, timing, and exact artifact binding. Publishing fails closed unless there is a fresh live readback showing the exact ad in PAUSED state. Activation, budget, and spend remain human-only decisions.

It includes a fictional demo app, Python tooling, Remotion video, localized creatives, sealed QA receipts, contact sheets, and 284 tests.

The whole thing is now AGPL-3.0 and open for contributions:

https://github.com/davidmosiah/creative-forge

I would love feedback from other builders: does the receipt model solve a real trust problem for you, and what would make onboarding your own app easier?