Define the procedure job before choosing a product

Treat “how to create photorealistic images using ai” as a step-by-step learning request, not as evidence that a feature exists. The action implied by the query is to create a planned asset or draft; 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. Before approval, preserve the rights memo, and ask the claims reviewer to record claim scope before the source comparison.

• Input: the highest-quality available source, provenance metadata, edit history, context, and an explicit review question Before approval, preserve the evidence table, and ask the channel editor to record visible continuity before the source comparison.
• Success: a cautious evidence record that distinguishes observable signals from a verified origin and preserves uncertainty Before approval, preserve the delivery checklist, and ask the identity reviewer to record evidence freshness before the source comparison.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the reference set, and ask the claims reviewer to record failure conditions before the source comparison.

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, sequence the work into reversible decisions and observable review points. 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. Before approval, preserve the test fixture, and ask the release approver to record destination fit before the release review.

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 this decision, preserve the control log, and ask the production lead to record disclosure clarity before the evidence refresh.

• Preserve the original and metadata For this decision, preserve the input snapshot, and ask the source custodian to record temporal order before the evidence refresh.
• Separate observation from attribution For this decision, preserve the evidence table, and ask the rights reviewer to record failure conditions before the evidence refresh.
• Escalate consequential decisions to expert review For this decision, preserve the rights memo, and ask the accessibility reviewer to record control availability before the evidence refresh.

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. For the named reviewer, preserve the authorization record, and ask the release approver to record input provenance before the bounded test.