Product Scene Variant Plan

How to use Product Scene Variant Plan

Scene generation should start with a small approved shot list instead of an unbounded combination of products and backgrounds. Preserve the specific scene instructions and human fidelity checks for each requested pair.

1. Record source products and only client-approved scene instructions.
2. List the exact pairs and quantities to produce, assigning a named fidelity reviewer.
3. Resolve reference gaps and compare every later variant with the authorized original before release.

Good to know

• Only explicit pairs are planned; duplicates are refused. At most 100 variants per pair and 1,000 requested variants across the plan.
• A named reviewer is an assignment, not completed approval. No generation, actual asset inspection, rights verification or fidelity certification occurs.
• Inputs are limited to 8,000 characters per field and 100 CSV data rows with exact displayed headers. Quoted commas, doubled quotes and quoted line endings are supported. Empty/duplicate identities and unsupported numeric values are refused; per-tool output bounds also apply.
• CSV text that resembles a spreadsheet formula is apostrophe-prefixed. This reduces formula execution risk without certifying every spreadsheet/import configuration.
• Deterministic browser-local work only. No AI model, upload, account connection, outreach, payment, saved input or automatic publication. Exports keep user-entered facts unverified; inspect edited drafts before sharing.