- 01
Define the workflow learning job
Treat “compositor face swap” 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. While evidence is current, preserve the claim inventory, and ask the accessibility reviewer to record revision intent before the release review.
- 02
Prepare inputs for identity transformation
For this topic, assemble documented consent from every identifiable person, authorized media, a legitimate purpose, and a disclosure 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. While evidence is current, preserve the control log, and ask the model evaluator to record format readiness before the production checkpoint.
- Confirm ownership, consent, and allowed reuse Before approval, preserve the continuity note, and ask the workflow owner to record evidence freshness before the fallback decision.
- Preserve an untouched source and version history Before approval, preserve the claim inventory, and ask the factual editor to record control availability before the fallback decision.
- Name the reviewer and acceptance condition Before approval, preserve the reference set, and ask the continuity editor to record human approval before the fallback decision.
- 03
Test observable controls for compositor face swap
A bounded evaluation should inspect identity scope, temporal consistency, expression fidelity, edit reversibility, provenance, and disclosure. 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 authorization record, and ask the brand reviewer to record disclosure clarity before the fallback decision.
- 04
Review evidence, safety, and policy boundaries
Do not enable impersonation, non-consensual face or body replacement, deceptive endorsements, or evasion of safeguards. Any identifiable face, body, or voice requires explicit permission, a legitimate purpose, disclosure where required, and a human check against impersonation or deceptive endorsement. 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. In the decision log, preserve the control log, and ask the continuity editor to record human approval before the editorial approval.
- 05
Approve a reversible production handoff
Before advancing “compositor face swap”, verify consent, inspect every frame for identity errors, preserve source records, and obtain a named human approval. 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 moving on, preserve the control log, and ask the model evaluator to record evidence freshness before the production checkpoint.