- 01
Define the access and terms evaluation job
Treat “relight for free” as a search job to investigate, not as proof that a SEELE feature exists. First verify current pricing, entitlement, limits, licensing, privacy, and delivery terms in first-party documentation. 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. Before delivery, preserve the failure note, and ask the delivery owner to record camera logic 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. Before delivery, preserve the brief version, and ask the factual editor to record disclosure clarity before the acceptance review.
- Confirm ownership, consent, and allowed reuse Before approval, preserve the authorization record, and ask the rights reviewer to record source fidelity before the workflow transfer.
- Preserve an untouched source and version history Before approval, preserve the failure note, and ask the channel editor to record human approval before the rights check.
- Name the reviewer and acceptance condition Before approval, preserve the evidence table, and ask the claims reviewer to record failure conditions before the rights check.
- 03
Test observable controls for relight for free
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 continuity note, and ask the creative lead to record visible continuity before the workflow transfer.
- 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. Words about free access, unlimited use, downloads, pricing, or licensing are query language rather than promises; verify current first-party terms before relying on them. 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. At handoff, preserve the continuity note, and ask the accessibility reviewer to record camera logic before the final sign-off.
- 05
Approve a reversible production handoff
Before advancing “relight for free”, 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. Before revision, preserve the brief version, and ask the delivery owner to record temporal order before the fallback decision.