Define the orientation job before choosing a product

Treat “what ai can view videos” as a broad orientation 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. While evidence is current, preserve the control log, and ask the source custodian to record format readiness before the reversible handoff.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve While evidence is current, preserve the input snapshot, and ask the continuity editor to record evidence freshness before the reversible handoff.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes While evidence is current, preserve the brief version, and ask the production lead to record visible continuity before the reversible handoff.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority While evidence is current, preserve the source ledger, and ask the source custodian to record identity consent before the reversible handoff.

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, 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 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. While evidence is current, preserve the claim inventory, and ask the delivery owner to record revision intent before the dated decision.

Apply the topic orientation boundary

Treat ambiguous or weakly related search language as a question to clarify. Do not turn it into a SEELE capability, endorsement, factual claim, or interactive workflow without evidence. Work from a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve. Review toward a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes. 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 failure note, and ask the model evaluator to record visible continuity before the rights check.

• Clarify the intended meaning Before approval, preserve the authorization record, and ask the delivery owner to record revision intent before the rights check.
• Choose an authorized example Before approval, preserve the decision history, and ask the creative lead to record control availability before the evidence refresh.
• Name the evidence needed for the next decision Before approval, preserve the handoff draft, and ask the policy reviewer to record evidence freshness before the evidence refresh.

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. Before delivery, preserve the input snapshot, and ask the model evaluator to record temporal order before the dated decision.