Define the orientation job before choosing a product

Treat “ии аватар” as a broad orientation request, not as evidence that a feature exists. The action implied by the query is to clarify the term and choose the next production decision; 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. Before moving on, preserve the review copy, and ask the identity reviewer to record failure conditions before the evidence refresh.

• Input: documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context Before moving on, preserve the test fixture, and ask the claims reviewer to record format readiness before the evidence refresh.
• Success: a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw Before moving on, preserve the decision history, and ask the channel editor to record reversal cost before the evidence refresh.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before moving on, preserve the handoff draft, and ask the release approver to record source fidelity before the rights check.

Use the category discovery method

Start by defining the term or named product in neutral language, then separate the reader's likely production job from brand recognition, spelling variants, and search popularity. Build a shortlist of questions before opening any workspace or vendor page. 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 category-discovery 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. Before moving on, preserve the evidence table, and ask the identity reviewer to record temporal order before the rights check.

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. For a controlled test, preserve the handoff draft, and ask the source custodian to record reversal cost before the editorial approval.

• Document identity consent For a controlled test, preserve the decision history, and ask the continuity editor to record format readiness before the editorial approval.
• Prevent deceptive attribution For a controlled test, preserve the authorization record, and ask the claims reviewer to record disclosure clarity before the production checkpoint.
• Review disclosure and withdrawal rights For a controlled test, preserve the failure note, and ask the delivery owner to record temporal order before the production checkpoint.

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

The handoff should state what the reader now understands, which interpretation remains uncertain, and which official source would be needed before a product-specific conclusion is publishable. 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 the named reviewer, preserve the handoff draft, and ask the creative lead to record failure conditions before the production checkpoint.