- 01
Define the tool evaluation job
Treat “skin enhancer” as a search job to investigate, not as proof that a SEELE feature exists. First clarify the requested job, observe current controls on a bounded test, and document workflow fit and evidence gaps. 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 this decision, preserve the delivery checklist, and ask the policy reviewer to record visible continuity before the evidence refresh.
- 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 this decision, preserve the handoff draft, and ask the brand reviewer to record revision intent before the delivery pass.
- Confirm ownership, consent, and allowed reuse Before approval, preserve the control log, and ask the delivery owner to record control availability before the final sign-off.
- Preserve an untouched source and version history Before approval, preserve the input snapshot, and ask the workflow owner to record disclosure clarity before the final sign-off.
- Name the reviewer and acceptance condition Before approval, preserve the handoff draft, and ask the rights reviewer to record temporal order before the final sign-off.
- 03
Test observable controls for skin enhancer
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. Before approval, preserve the brief version, and ask the continuity editor to record source fidelity before the final sign-off.
- 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. While evidence is current, preserve the evidence table, and ask the workflow owner to record source fidelity before the production checkpoint.
- 05
Approve a reversible production handoff
Before advancing “skin enhancer”, 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 continuity note, and ask the continuity editor to record visible continuity before the release review.