Product Rotation Generator

Define the workflow learning job

Treat “product rotation” as a search job to investigate, not as proof that a SEELE feature exists. First turn the query into a repeatable sequence with explicit inputs, review points, and a reversible handoff. Write the intended audience, source owner, desired change, protected details, reviewer, and delivery condition before selecting any interface or model. That brief keeps the evaluation specific and makes an unsupported assumption visible early. Before revision, preserve the input snapshot, and ask the source custodian to record revision intent before the workflow transfer.

Prepare inputs for motion effects

For this topic, assemble the authorized shot, desired motion cue, protected scene elements, timing, and compositing requirements. Record where each source came from, who may use it, and what must remain unchanged. Use a small representative asset for the first pass, keep the original untouched, and define a fallback route so experimentation cannot silently become the production master. Before revision, preserve the continuity note, and ask the source custodian to record source fidelity before the acceptance review.

• Confirm ownership, consent, and allowed reuse While evidence is current, preserve the reference set, and ask the factual editor to record control availability before the rights check.
• Preserve an untouched source and version history While evidence is current, preserve the delivery checklist, and ask the brand reviewer to record disclosure clarity before the rights check.
• Name the reviewer and acceptance condition While evidence is current, preserve the continuity note, and ask the release approver to record camera logic before the rights check.

Test observable controls for product rotation

A bounded evaluation should inspect motion direction, intensity, camera relationship, masks, edge behavior, temporal coherence, and reversibility. Change one meaningful variable at a time and record the date, workspace, account context, input, setting, result, and failure. Topic selection can prioritize the question, but it does not establish availability, quality, speed, licensing, or a supported SEELE workflow. While evidence is current, preserve the evidence table, and ask the workflow owner to record source fidelity before the rights check.

Review evidence, safety, and policy boundaries

Treat effect names as evaluation topics, not proof of a one-click SEELE feature or guaranteed artifact-free result. Use only authorized media, separate observed behavior from marketing language, and check current first-party documentation for any product-specific claim. For third-party products, competitors, plans, models, and platform rules, attach a verification date and primary source; an absent statement is an evidence gap rather than proof of a limitation. At this stage, preserve the brief version, and ask the policy reviewer to record temporal order before the delivery pass.

Approve a reversible production handoff

Before advancing “product rotation”, inspect transitions and edges across frames, compare against the original shot, and retain a clean fallback plate. Document remaining manual work, unresolved evidence, destination requirements, and the person accepting the result. The handoff should preserve sources and test notes, allow correction, and avoid promises about output quality, turnaround, business performance, publishing, or access that the evidence does not support. Before delivery, preserve the handoff draft, and ask the identity reviewer to record claim scope before the fallback decision.