Define the orientation job before choosing a product

Treat “echo clone ai” 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 this stage, preserve the claim inventory, and ask the model evaluator to record identity consent before the reversible handoff.

• Input: documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context At this stage, preserve the continuity note, and ask the creative lead to record input provenance before the reversible handoff.
• Success: a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw Before revision, preserve the failure note, and ask the channel editor to record reversal cost before the final sign-off.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At this stage, preserve the authorization record, and ask the rights reviewer to record claim scope before the reversible handoff.

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 control log, and ask the policy reviewer to record control availability 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. For a reversible workflow, preserve the authorization record, and ask the workflow owner to record camera logic before the acceptance review.

• Document identity consent For a reversible workflow, preserve the failure note, and ask the rights reviewer to record revision intent before the acceptance review.
• Prevent deceptive attribution For a reversible workflow, preserve the handoff draft, and ask the creative lead to record format readiness before the workflow transfer.
• Review disclosure and withdrawal rights For a reversible workflow, preserve the decision history, and ask the model evaluator to record evidence freshness before the workflow transfer.

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 approval, preserve the control log, and ask the production lead to record failure conditions before the bounded test.