Define the orientation job before choosing a product

Treat “ai older” 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. At handoff, preserve the delivery checklist, and ask the production lead to record disclosure clarity before the release review.

• Input: documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context At handoff, preserve the reference set, and ask the accessibility reviewer to record control availability before the release review.
• Success: a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw At handoff, preserve the rights memo, and ask the accessibility reviewer to record reversal cost before the production checkpoint.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At handoff, preserve the evidence table, and ask the rights reviewer to record claim scope before the release review.

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. At handoff, preserve the handoff draft, and ask the policy reviewer to record control availability before the production checkpoint.

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. In the decision log, preserve the brief version, and ask the policy reviewer to record format readiness before the delivery pass.

• Document identity consent In the decision log, preserve the source ledger, and ask the creative lead to record failure conditions before the delivery pass.
• Prevent deceptive attribution In the decision log, preserve the reference set, and ask the policy reviewer to record visible continuity before the rights check.
• Review disclosure and withdrawal rights In the decision log, preserve the delivery checklist, and ask the creative lead to record identity consent before the rights check.

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 this decision, preserve the evidence table, and ask the model evaluator to record format readiness before the fallback decision.