- 01
Define the tool evaluation job
Treat “real avatar” 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. While evidence is current, preserve the test fixture, and ask the brand reviewer to record human approval before the acceptance review.
- 02
Prepare inputs for avatar creation
For this topic, assemble an authorized identity brief, visual references, intended performance, disclosure plan, and delivery context. 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 rights memo, and ask the channel editor to record camera logic before the fallback decision.
- Confirm ownership, consent, and allowed reuse Before approval, preserve the source ledger, and ask the workflow owner to record evidence freshness before the acceptance review.
- Preserve an untouched source and version history Before approval, preserve the brief version, and ask the delivery owner to record format readiness before the acceptance review.
- Name the reviewer and acceptance condition Before approval, preserve the review copy, and ask the continuity editor to record human approval before the acceptance review.
- 03
Test observable controls for real avatar
A bounded evaluation should inspect likeness boundaries, stylization, expression range, wardrobe continuity, and identity 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 input snapshot, and ask the factual editor to record revision intent before the fallback decision.
- 04
Review evidence, safety, and policy boundaries
Never use a real person's likeness without permission or present a synthetic performance as an authentic endorsement. 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. Before delivery, preserve the failure note, and ask the continuity editor to record human approval before the source comparison.
- 05
Approve a reversible production handoff
Before advancing “real avatar”, confirm identity consent, visual consistency, appropriate disclosure, and suitability for the intended audience. 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 input snapshot, and ask the policy reviewer to record evidence freshness before the release review.