Define the verification job before choosing a product

Treat “can you upload videos to grok” as a yes-or-no verification request, not as evidence that a feature exists. The action implied by the query is to add or connect an authorized element; the working object is named model or platform. 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 moving on, preserve the reference set, and ask the continuity editor to record identity consent before the production checkpoint.

• Input: non-sensitive test media, the current privacy terms, retention details, sharing defaults, and an authorized data owner Before moving on, preserve the delivery checklist, and ask the delivery owner to record claim scope before the production checkpoint.
• Success: a documented decision about whether the service and workflow meet the project's privacy, retention, visibility, and deletion requirements Before moving on, preserve the evidence table, and ask the source custodian to record destination fit before the editorial approval.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before moving on, preserve the rights memo, and ask the continuity editor to record temporal order before the editorial approval.

Use the dated model guide method

Record the exact provider and version named by the query, the access surface being evaluated, the verification date, and the production job. Turn inputs, controls, limits, pricing, privacy, and output behavior into evidence questions until primary sources are attached. 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 model-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 moving on, preserve the decision history, and ask the accessibility reviewer to record claim scope before the editorial approval.

Apply the privacy and data governance boundary

Do not infer that uploads or generations are private, public, retained, deleted, or training-exempt. Verify each condition in current first-party terms and account controls. Work from non-sensitive test media, the current privacy terms, retention details, sharing defaults, and an authorized data owner. Review toward a documented decision about whether the service and workflow meet the project's privacy, retention, visibility, and deletion requirements. 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. At the next gate, preserve the review copy, and ask the brand reviewer to record reversal cost before the acceptance review.

• Use non-sensitive evaluation media At the next gate, preserve the test fixture, and ask the factual editor to record claim scope before the fallback decision.
• Verify visibility and retention At the next gate, preserve the claim inventory, and ask the identity reviewer to record reversal cost before the fallback decision.
• Record the responsible data owner At the next gate, preserve the continuity note, and ask the claims reviewer to record source fidelity before the scope confirmation.

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

The record must distinguish documented facts, direct observations, and open questions. A similar name, search result, or third-party demonstration is not enough to establish current availability in SEELE or elsewhere. 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 delivery checklist, and ask the claims reviewer to record revision intent before the controlled revision.