Attaching a video does not necessarily tell a unified generator to edit that exact clip. The video may be interpreted as a reference for a new result. Alibaba’s Wan 3.0 guide routes tasks using media types and the requested operation. Make the editing intent explicit and inspect the actual request mode rather than assuming the attachment determines it.
Specify the source-preservation obligation
Write one sentence naming the source clip and the permitted change. For example: “Edit this supplied kitchen clip by changing only the apron color; retain the person, action order and camera movement.” This is a hypothetical brief, not a promise that the model can preserve every item. It gives reviewers something concrete to examine.
Contrast that with “Create a kitchen demonstration inspired by this clip.” The latter permits a new scene and cannot serve as an approval specification for editing. If both requests appear in the same paragraph, resolve the conflict first. A model cannot infer which source facts are mandatory simply because they matter privately to the client.
Verify the request route before submission
Inspect the selected operation, uploaded media roles and the current documentation. If the interface exposes separate editing and reference-generation entries, select the one matching the brief. With an API, record the documented field arrangement without inventing a universal edit flag. Keep the source filename and actual request identifier together.
| Source property | Allowed to change? | Evidence to compare |
|---|---|---|
| Person | No | Recognizable appearance throughout |
| Action sequence | No | Same meaningful steps in order |
| Apron color | Yes | Intended new color without changed garment structure |
| Camera path | No, in this example | Comparable movement and framing |
The acceptance record should be shorter than a generic wish list. Include only properties the job genuinely needs to preserve. Unsupported preservation requirements should be acknowledged before generation.
Compare against the source, not a memory
Review the source and result side by side at matching events: the first hand movement, opening of a cupboard, and the final placement of the object. Exact frame alignment may be inappropriate if the result changes timing, so record that timing change separately. Identify substituted actions, missing people and newly invented details even when the result looks plausible.
Do not accept visual resemblance as proof of source editing. A newly generated room may share the same colors but replace the real countertop, product or gesture. Conversely, an editing attempt can still alter unwanted content. Correct routing is necessary for the intended contract, but it does not establish fidelity.
Decide what the result can honestly be called
If the source-preservation obligations fail, classify the clip as a rejected edit or seek explicit approval to use it as newly generated illustrative material. Do not silently relabel it as a successful edit. Preserve the original so a deterministic repair or another supported route remains possible.
In an Imagild project, identify whether a video is an editing source, motion evidence or stylistic reference. Those roles should travel with the file. External unified routing rules do not establish an identical Imagild API, and a reference attachment alone does not certify that an existing clip was modified.
Sources and scope
Filled acceptance record: editing intent
This is a constructed editorial exercise, not a reported generation or software test. Its purpose is to make the decision observable before spending on a more complicated version.
| Review item | Hypothetical evidence | Decision and next action |
|---|---|---|
| Main requirement | A new kitchen resembles the source but replaces the real countertop. | Hold this candidate: reject it as a preserved-source edit; classify any approved use as a new interpretation. |
| Source relationship | The current source and proposed change remain separately identified. | Release the written brief for review only; a clear plan is not an approved generated clip. |
| Handoff | The record names the rejected behavior and the relevant interval. | Keep the source, candidate and decision together so the next revision can be judged against the same requirement. |
Watch the complete interval before isolating frames. Write down where the problem first becomes visible and whether it persists to the end. A later attractive frame does not cancel an earlier failure. Change the relevant input or production decision before adding unrelated style instructions. If an external editor is used, record that finishing step separately from generation.
Current Imagild boundary
Use /en/film-script to organize a written plan and /en/film-prompt only for a currently supported reference-video recreation workflow. Check the actual selected input roles. The old video-prompt and editor routes do not establish a native analyzer, exact camera lock, existing-clip editor or frame-complete transcript. Manual source review remains valid even when no automated analysis is available. External application instructions above belong to the named vendor, not to Imagild.
Source checked for the transferable planning principle
- Runway Image to Video Prompting Guide: distinguishes image-established appearance from instructions for motion and temporal progression. The vendor's supported modes and results are not an Imagild feature contract.
November 13, 2026 editorial update. The worksheet and proposed procedures are illustrative. No new generation, physical measurement, success-rate study, citation measurement or production deployment was performed.