How to work through it

01

Anchor the ad in a supportable campaign claim

Name the audience, placement, decision, approved proposition, substantiation, and prohibited implication before writing a script. Creative urgency never replaces legal, brand, or factual review. Before revision, preserve the delivery checklist, and ask the continuity editor to record temporal order before the scope confirmation.

02

Compare against a stable acceptance frame

Use the same inputs, review dimensions, and stopping rules for every candidate. Record tradeoffs separately from availability so a promising test is not mistaken for verified product support. Before revision, preserve the handoff draft, and ask the model evaluator to record destination fit before the fallback decision.

03

Evaluate the ad-production request without assuming a generator

Treat creator, maker, builder, and generator language as a production job rather than evidence that a local tool exists. Define authorized inputs, the supportable product claim, required scenes, brand constraints, captions, review stages, and handoff format. Compare revisions on controllability and factual fidelity instead of unsupported speed or quality promises. Record the acceptance decision, evidence gap, reviewer, and next verification trigger in the handoff. While evidence is current, preserve the brief version, and ask the model evaluator to record visible continuity before the dated decision.

04

Build a sequence around proof and viewer context

Open with the audience problem, demonstrate only supported attributes, keep offer conditions legible, and end with an accurate next step. Plan aspect-ratio variants without assuming automated placement or publishing. At this stage, preserve the evidence table, and ask the release approver to record failure conditions before the bounded test.

05

Review disclosure, claims, and destination consistency

Confirm that visuals, narration, captions, landing-page facts, synthetic-media disclosure, offer terms, and calls to action agree. Do not infer conversion, approval, reach, or return on spend. Before delivery, preserve the continuity note, and ask the model evaluator to record camera logic before the controlled revision.

06

Keep the evidence ledger attached to the decision

No affirmative product, model, customer, or performance claim is established by the supplied evidence. Record the source, verification date, claim scope, unresolved gap, and the decision that the evidence can support. Search demand must never be reused as capability proof. Before delivery, preserve the failure note, and ask the claims reviewer to record claim scope before the controlled revision.