Define the orientation job before choosing a product

Treat “ai grillz” 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. At this stage, preserve the rights memo, and ask the claims reviewer to record claim scope before the release review.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve At this stage, preserve the evidence table, and ask the channel editor to record visible continuity before the release review.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes At this stage, preserve the delivery checklist, and ask the identity reviewer to record evidence freshness before the release review.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At this stage, preserve the reference set, and ask the claims reviewer to record failure conditions before the release review.

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. At this stage, preserve the test fixture, and ask the release approver to record destination fit before the production checkpoint.

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. For the named reviewer, preserve the control log, and ask the production lead to record disclosure clarity before the source comparison.

• Clarify the intended meaning For the named reviewer, preserve the input snapshot, and ask the source custodian to record temporal order before the source comparison.
• Choose an authorized example For the named reviewer, preserve the evidence table, and ask the rights reviewer to record failure conditions before the source comparison.
• Name the evidence needed for the next decision For the named reviewer, preserve the rights memo, and ask the accessibility reviewer to record control availability before the source comparison.

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. Before moving on, preserve the authorization record, and ask the release approver to record input provenance before the final sign-off.