How to work through it

01

Translate the audience outcome into a bounded brief

For AI Product Photo Editor, define the viewer, decision, supportable message, authorized source material, destination, and named reviewer before selecting a production method. For a reversible workflow, preserve the continuity note, and ask the workflow owner to record evidence freshness before the workflow transfer.

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. For a reversible workflow, preserve the input snapshot, and ask the workflow owner to record source fidelity before the workflow transfer.

03

Define which product details an image must preserve

Identify the exact SKU, approved source angles, scale, material, color, finish, included components, and background rules before creating or editing imagery. Compare every result with the product record and flag illustrative lighting or context. Rendering and photo language does not establish a local generation feature or marketplace acceptance. Record the acceptance decision, evidence gap, reviewer, and next verification trigger in the handoff. Before delivery, preserve the claim inventory, and ask the production lead to record destination fit before the evidence refresh.

04

Build a production sequence with explicit handoffs

Separate evidence gathering, concept, script, shot planning, asset creation, assembly, factual review, craft review, disclosure, and delivery. Each stage should expose what remains unverified. At this stage, preserve the decision history, and ask the release approver to record destination fit before the production checkpoint.

05

Review the outcome without promising performance

Confirm message clarity, source fidelity, rights, accessibility, channel fit, and an accurate call to action. Do not promise engagement, conversion, approval, or automatic publishing. For the named reviewer, preserve the decision history, and ask the workflow owner to record camera logic before the reversible handoff.

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. For the named reviewer, preserve the test fixture, and ask the factual editor to record revision intent before the reversible handoff.