Define the orientation job before choosing a product

Treat “грок видео” 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. Before approval, preserve the claim inventory, and ask the accessibility reviewer to record control availability before the delivery pass.

• Input: the exact product, provider, version, region, account surface, production job, and verification date Before approval, preserve the continuity note, and ask the rights reviewer to record failure conditions before the delivery pass.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps Before approval, preserve the failure note, and ask the identity reviewer to record temporal order before the delivery pass.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the authorization record, and ask the production lead to record disclosure clarity before the delivery pass.

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. Before approval, preserve the control log, and ask the model evaluator to record identity consent before the delivery pass.

Apply the named platform or model facts boundary

Do not infer SEELE support, model access, quality, legitimacy, censorship, ownership, API behavior, or compatibility from the query. Verify first-party documentation and direct observations on the use date. Work from the exact product, provider, version, region, account surface, production job, and verification date. Review toward a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps. 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 authorization record, and ask the brand reviewer to record temporal order before the production checkpoint.

• Confirm exact provider and version For this decision, preserve the failure note, and ask the production lead to record revision intent before the production checkpoint.
• Date every changing fact For this decision, preserve the handoff draft, and ask the rights reviewer to record human approval before the editorial approval.
• Keep observations separate from documentation For this decision, preserve the decision history, and ask the accessibility reviewer to record failure conditions before the editorial approval.

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. While evidence is current, preserve the control log, and ask the continuity editor to record format readiness before the rights check.