Define the orientation job before choosing a product

Treat “what will i look like when i grow up” as a broad orientation request, not as evidence that a feature exists. The action implied by the query is to resolve a factual or conceptual question; the working object is editorial topic. Write the intended audience or user, authorized input, desired change, review owner, and finished handoff. Also state what the task excludes. This brief keeps search wording from turning into an unsupported promise about SEELE, a named vendor, a model, or an automatic result. For a controlled test, preserve the input snapshot, and ask the policy reviewer to record camera logic before the scope confirmation.

• Input: documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context For a controlled test, preserve the control log, and ask the identity reviewer to record disclosure clarity before the scope confirmation.
• Success: a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw For a controlled test, preserve the source ledger, and ask the identity reviewer to record format readiness before the fallback decision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For a controlled test, preserve the brief version, and ask the claims reviewer to record human approval before the fallback decision.

Use the concept explanation method

Move from a plain-language definition to one visual or production example, one counterexample, and a small observation exercise. Explain the durable concept first; treat named software, model behavior, and trend language as separate evidence questions. For this query, clarify the intended meaning and production job before choosing a process or product. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The concepts-explainers classification determines this learning sequence, while the authoritative taxonomy remains the only owner of the route. This page supplies editorial copy and cannot silently change the category, subhub, or URL. For a controlled test, preserve the continuity note, and ask the policy reviewer to record claim scope before the final sign-off.

Apply the identity and consent boundary

Do not impersonate, fabricate endorsement, sexualize, harass, or manipulate an identity without explicit authorization. Face swaps, age changes, avatars, and voice work require consent and disclosure review. Work from documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context. Review toward a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw. A polished draft is not enough: the reviewer must be able to see which source supports each factual statement, who authorized each asset or identity, and which product behavior is still an unanswered test question. Topic selection alone never establishes safety, availability, quality, or permission. Before revision, preserve the evidence table, and ask the brand reviewer to record reversal cost before the workflow transfer.

• Document identity consent Before revision, preserve the rights memo, and ask the release approver to record format readiness before the workflow transfer.
• Prevent deceptive attribution Before revision, preserve the control log, and ask the channel editor to record failure conditions before the workflow transfer.
• Review disclosure and withdrawal rights Before revision, preserve the input snapshot, and ask the claims reviewer to record control availability before the workflow transfer.

Record evidence, review the handoff, and name the next check

A useful explanation lets a reader distinguish the concept from a nearby idea and apply it to a new example without depending on a vendor interface or an unsupported capability statement. Run separate passes for craft, factual accuracy, identity and source rights, safety, accessibility, and destination requirements. Record the source and verification date for any changing platform, model, price, policy, privacy, export, or compatibility statement. If primary evidence is missing, publish the item only as a question or editorial planning step. The finished handoff must name the approver and preserve a path back to the authorized original. For a reversible workflow, preserve the brief version, and ask the factual editor to record format readiness before the fallback decision.