Image Editing, Variations, and Iteration
Editing workflows may combine an input image, mask, prompt, and model-specific controls. Keep original assets immutable, store derived outputs separately, and record the relationship between versions. Make user intent explicit when editing an image rather than generating a replacement from scratch.
For creative tools, offer preview, retry, undo, and comparison. Do not promise pixel-perfect control unless the API and workflow provide it. When images include people or sensitive content, follow consent, privacy, and applicable policy requirements.
Asset lineage
Original asset
-> edit request (prompt + mask + parameters)
-> generated version 1
-> user feedback
-> generated version 2
-> approved final asset💡 Lineage allows users to compare outputs, reproduce a workflow, and return to the original. Record provider job IDs and parameter versions when useful.
Key Takeaways
- Record inputs and parameters for reproducibility.
- Keep originals and derivatives separate.
- Offer user control over preview, retry, and final selection.
Knowledge Check
What is a useful design rule for image editing history?