Define the orientation job before choosing a product

Treat “ai news anchor software” 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 failure note, and ask the creative lead to record input provenance before the rights check.

• Input: documented permission for every identifiable face, voice, avatar, likeness, or personal image plus an approved use context At handoff, preserve the authorization record, and ask the continuity editor to record revision intent before the rights check.
• Success: a transparent, non-deceptive identity treatment that preserves consent, dignity, provenance, and the right to withdraw At handoff, preserve the claim inventory, and ask the source custodian to record temporal order before the rights check.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At handoff, preserve the continuity note, and ask the production lead to record disclosure clarity before the rights check.

Use the how-to method method

Translate the request into an input, a reversible action, a checkpoint, and a finished handoff. Practice on a duplicate or non-sensitive sample, preserve the original, and stop when authorization, account access, safety, or factual uncertainty appears. 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 how-to-guides 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 brief version, and ask the rights reviewer to record camera logic before the evidence refresh.

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 continuity note, and ask the source custodian to record camera logic before the dated decision.

• Document identity consent Before approval, preserve the claim inventory, and ask the continuity editor to record input provenance before the dated decision.
• Prevent deceptive attribution Before approval, preserve the test fixture, and ask the model evaluator to record camera logic before the reversible handoff.
• Review disclosure and withdrawal rights Before approval, preserve the review copy, and ask the rights reviewer to record revision intent before the reversible handoff.

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

The result should be reproducible from the written decisions while leaving product-specific buttons, limits, and account behavior to current official documentation rather than invented steps. 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. At handoff, preserve the continuity note, and ask the workflow owner to record destination fit before the release review.