- 01
Define the workflow learning job
Treat “fix lighting in photos” 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 a controlled test, preserve the test fixture, and ask the model evaluator to record identity consent before the fallback decision.
- 02
Prepare inputs for quality enhancement
For this topic, assemble the best authorized source, a diagnosed defect, protected details, target display conditions, and an acceptance threshold. 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 a controlled test, preserve the rights memo, and ask the accessibility reviewer to record control availability before the fallback decision.
- Confirm ownership, consent, and allowed reuse Before approval, preserve the source ledger, and ask the accessibility reviewer to record human approval before the final sign-off.
- Preserve an untouched source and version history For a controlled test, preserve the brief version, and ask the rights reviewer to record source fidelity before the reversible handoff.
- Name the reviewer and acceptance condition For a controlled test, preserve the review copy, and ask the model evaluator to record claim scope before the reversible handoff.
- 03
Test observable controls for fix lighting in photos
A bounded evaluation should inspect detail recovery, noise handling, sharpness, color stability, temporal consistency, and preservation of intentional texture. 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 a controlled test, preserve the input snapshot, and ask the production lead to record temporal order before the reversible handoff.
- 04
Review evidence, safety, and policy boundaries
Enhancement cannot restore facts absent from the source, and this page makes no resolution, speed, or quality guarantee. 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 failure note, and ask the model evaluator to record claim scope before the rights check.
- 05
Approve a reversible production handoff
Before advancing “fix lighting in photos”, compare at native size, inspect faces and text, review motion when applicable, and reject invented or oversharpened detail. 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. At this stage, preserve the input snapshot, and ask the rights reviewer to record disclosure clarity before the release review.