Define the verification job before choosing a product

Treat “is grok image generation free” 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 still image. 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 reference set, and ask the rights reviewer to record visible continuity before the fallback decision.

• Input: the named plan or product, region and account context, intended commercial use, current official terms, and an evaluation date Before approval, preserve the delivery checklist, and ask the accessibility reviewer to record claim scope before the fallback decision.
• Success: a dated access decision that distinguishes trials, credits, exports, licenses, and commercial rights instead of treating the word free as a permanent promise Before approval, preserve the evidence table, and ask the model evaluator to record destination fit before the acceptance review.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the rights memo, and ask the rights reviewer to record disclosure clarity before the acceptance review.

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 approval, preserve the decision history, and ask the policy reviewer to record claim scope before the acceptance review.

Apply the price, access, and usage terms boundary

Search wording does not prove free access, a download, rolling credits, monetization, commercial rights, or any entitlement. Verify current first-party pricing, plan limits, license terms, and platform policy. Work from the named plan or product, region and account context, intended commercial use, current official terms, and an evaluation date. Review toward a dated access decision that distinguishes trials, credits, exports, licenses, and commercial rights instead of treating the word free as a permanent promise. 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 the working record, preserve the review copy, and ask the identity reviewer to record input provenance before the scope confirmation.

• Date the plan and region For the working record, preserve the test fixture, and ask the claims reviewer to record revision intent before the scope confirmation.
• Separate access from usage rights For the working record, preserve the claim inventory, and ask the rights reviewer to record input provenance before the final sign-off.
• Record export and credit conditions For the working record, preserve the continuity note, and ask the model evaluator to record revision intent before the final sign-off.

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. At this stage, preserve the delivery checklist, and ask the model evaluator to record control availability before the delivery pass.