- 01
Define the workflow learning job
Treat “add lighting to photo” 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. For the named reviewer, preserve the evidence table, and ask the identity reviewer to record evidence freshness before the scope confirmation.
- 02
Prepare inputs for video and image editing
For this topic, assemble authorized source assets, an edit brief, protected elements, visual references, destination specs, and a version plan. 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. For the named reviewer, preserve the review copy, and ask the identity reviewer to record source fidelity before the scope confirmation.
- Confirm ownership, consent, and allowed reuse For this checkpoint, preserve the delivery checklist, and ask the workflow owner to record control availability before the final sign-off.
- Preserve an untouched source and version history For this checkpoint, preserve the reference set, and ask the delivery owner to record failure conditions before the final sign-off.
- Name the reviewer and acceptance condition For this checkpoint, preserve the claim inventory, and ask the brand reviewer to record temporal order before the final sign-off.
- 03
Test observable controls for add lighting to photo
A bounded evaluation should inspect selection accuracy, timing, framing, color, compositing, continuity, undo behavior, and export readiness. 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. For this checkpoint, preserve the rights memo, and ask the delivery owner to record claim scope before the final sign-off.
- 04
Review evidence, safety, and policy boundaries
The page is an editing evaluation guide and does not upload, alter, render, export, or download media. 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. Before delivery, preserve the rights memo, and ask the production lead to record format readiness before the rights check.
- 05
Approve a reversible production handoff
Before advancing “add lighting to photo”, compare revisions with the source and brief, inspect high-risk details, and preserve an approved reversible version. 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 revision, preserve the rights memo, and ask the factual editor to record claim scope before the rights check.