- 01
Define the tool evaluation job
Treat “swapface” 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 a controlled test, preserve the input snapshot, and ask the claims reviewer to record temporal order before the delivery pass.
- 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. For a controlled test, preserve the continuity note, and ask the claims reviewer to record identity consent before the evidence refresh.
- Confirm ownership, consent, and allowed reuse Before approval, preserve the reference set, and ask the model evaluator to record destination fit before the reversible handoff.
- Preserve an untouched source and version history Before approval, preserve the delivery checklist, and ask the rights reviewer to record disclosure clarity before the reversible handoff.
- Name the reviewer and acceptance condition Before approval, preserve the continuity note, and ask the accessibility reviewer to record camera logic before the reversible handoff.
- 03
Test observable controls for swapface
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 evidence table, and ask the creative lead to record source fidelity before the reversible handoff.
- 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. At handoff, preserve the brief version, and ask the delivery owner to record temporal order before the scope confirmation.
- 05
Approve a reversible production handoff
Before advancing “swapface”, 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 revision, preserve the handoff draft, and ask the continuity editor to record source fidelity before the editorial approval.