How to work through it
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 delivery, preserve the source ledger, and ask the factual editor to record destination fit before the delivery pass.
Name the audience, source materials, creative constraints, reviewer, and delivery condition first. This makes the workflow actionable without assuming that a product will automate every step. Before delivery, preserve the authorization record, and ask the channel editor to record control availability before the evidence refresh.
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. For a controlled test, preserve the reference set, and ask the channel editor to record disclosure clarity before the delivery pass.
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. In the decision log, preserve the test fixture, and ask the factual editor to record identity consent before the scope confirmation.
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 moving on, preserve the test fixture, and ask the channel editor to record revision intent before the bounded test.
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 moving on, preserve the decision history, and ask the release approver to record camera logic before the bounded test.
