Define the orientation job before choosing a product

Treat “ai idols” 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. For the named reviewer, preserve the decision history, and ask the brand reviewer to record revision intent before the final sign-off.

• Input: documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context For the named reviewer, preserve the handoff draft, and ask the factual editor to record temporal order before the final sign-off.
• Success: a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw For the named reviewer, preserve the review copy, and ask the channel editor to record identity consent before the final sign-off.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For the named reviewer, preserve the test fixture, and ask the release approver to record visible continuity before the final sign-off.

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 revision, preserve the reference set, and ask the claims reviewer to record camera logic before the reversible handoff.

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 approval, preserve the test fixture, and ask the rights reviewer to record visible continuity before the production checkpoint.

• Document identity consent Before approval, preserve the review copy, and ask the accessibility reviewer to record claim scope before the production checkpoint.
• Prevent deceptive attribution Before approval, preserve the continuity note, and ask the continuity editor to record identity consent before the release review.
• Review disclosure and withdrawal rights Before approval, preserve the claim inventory, and ask the delivery owner to record claim scope before the release review.

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. Before delivery, preserve the reference set, and ask the workflow owner to record evidence freshness before the fallback decision.