Define the orientation job before choosing a product

Treat “realistic skin 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. In the decision log, preserve the brief version, and ask the creative lead to record source fidelity before the controlled revision.

• Input: the highest-quality available source, provenance metadata, edit history, context, and an explicit review question In the decision log, preserve the source ledger, and ask the model evaluator to record human approval before the source comparison.
• Success: a cautious evidence record that distinguishes observable signals from a verified origin and preserves uncertainty In the decision log, preserve the control log, and ask the model evaluator to record destination fit before the controlled revision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority In the decision log, preserve the input snapshot, and ask the rights reviewer to record disclosure clarity before the controlled revision.

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. In the decision log, preserve the failure note, and ask the identity reviewer to record human approval before the controlled revision.

Apply the authenticity and provenance signals boundary

Visual appearance alone cannot prove whether media is AI-generated, real, edited, legitimate, or attributable to a named system. Avoid definitive labels without reliable provenance. Work from the highest-quality available source, provenance metadata, edit history, context, and an explicit review question. Review toward a cautious evidence record that distinguishes observable signals from a verified origin and preserves uncertainty. 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 source ledger, and ask the brand reviewer to record failure conditions before the rights check.

• Preserve the original and metadata For a reversible workflow, preserve the brief version, and ask the factual editor to record human approval before the rights check.
• Separate observation from attribution For a reversible workflow, preserve the delivery checklist, and ask the brand reviewer to record identity consent before the acceptance review.
• Escalate consequential decisions to expert review For a reversible workflow, preserve the reference set, and ask the factual editor to record input provenance before the acceptance 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 revision, preserve the source ledger, and ask the delivery owner to record destination fit before the source comparison.