Define the verification job before choosing a product

Treat “is holy groove ai generated” as a yes-or-no verification request, not as evidence that a feature exists. The action implied by the query is to resolve a factual or conceptual question; 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 continuity note, and ask the accessibility reviewer to record camera logic before the release review.

• Input: the highest-quality available source, provenance metadata, edit history, context, and an explicit review question At handoff, preserve the claim inventory, and ask the production lead to record input provenance before the release review.
• Success: a cautious evidence record that distinguishes observable signals from a verified origin and preserves uncertainty At handoff, preserve the authorization record, and ask the source custodian to record visible continuity before the release review.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At handoff, preserve the failure note, and ask the policy reviewer to record claim scope before the release review.

Use the concept explanation method

Move from a plain-language definition to one visual or production example, one counterexample, and a small observation exercise. Explain the durable concept first; treat named software, model behavior, and trend language as separate evidence questions. For this query, identify the claim, the authoritative source, the date, and the conditions that could change the answer. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The concepts-explainers 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 input snapshot, and ask the accessibility reviewer to record evidence freshness before the production checkpoint.

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 checkpoint, preserve the claim inventory, and ask the accessibility reviewer to record camera logic before the scope confirmation.

• Preserve the original and metadata For this checkpoint, preserve the continuity note, and ask the rights reviewer to record disclosure clarity before the scope confirmation.
• Separate observation from attribution For this checkpoint, preserve the review copy, and ask the policy reviewer to record camera logic before the fallback decision.
• Escalate consequential decisions to expert review For this checkpoint, preserve the test fixture, and ask the identity reviewer to record disclosure clarity before the fallback decision.

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

A useful explanation lets a reader distinguish the concept from a nearby idea and apply it to a new example without depending on a vendor interface or an unsupported capability statement. 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 a reversible workflow, preserve the decision history, and ask the rights reviewer to record format readiness before the acceptance review.