How to work through it

01

Start from verified product facts and approved assets

Identify the exact product variant, observable attributes, approved claims, source images, usage context, and destination requirements. Treat missing product evidence as a blocking gap. Before moving on, preserve the source ledger, and ask the identity reviewer to record disclosure clarity before the fallback decision.

02

Plan the handoff before producing assets

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 moving on, preserve the authorization record, and ask the model evaluator to record destination fit before the scope confirmation.

03

Build the commerce sequence from the verified product record

Map each scene to an approved product fact, audience question, usage condition, or accurate next step. Preserve variant, packaging, color, scale, and included-item fidelity across the sequence. Keep storefront integration, catalog publishing, price, inventory, and platform acceptance outside the claim boundary unless separately verified and dated. Record the acceptance decision, evidence gap, reviewer, and next verification trigger in the handoff. In the decision log, preserve the reference set, and ask the claims reviewer to record destination fit before the evidence refresh.

04

Plan a product sequence that preserves fidelity

Move from context to legible product detail, demonstrate only supportable behavior, and close with an accurate next step. Flag any stylization that could alter color, scale, packaging, included items, or function. At handoff, preserve the test fixture, and ask the rights reviewer to record format readiness before the workflow transfer.

05

Validate the listing and handoff

Compare visuals and narration with the approved product record, check marketplace specifications and disclosure, and keep catalog publishing outside the workflow unless independently verified. Before revision, preserve the test fixture, and ask the source custodian to record source fidelity 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. Before revision, preserve the decision history, and ask the production lead to record claim scope before the reversible handoff.