Define the sourcing job before choosing a product

Treat “where can i generate” as a source-selection request, not as evidence that a feature exists. The action implied by the query is to create a planned asset or draft; 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. For the working record, preserve the authorization record, and ask the rights reviewer to record claim scope before the editorial approval.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve For the working record, preserve the failure note, and ask the channel editor to record reversal cost before the bounded test.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes For the working record, preserve the continuity note, and ask the creative lead to record input provenance before the editorial approval.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For the working record, preserve the claim inventory, and ask the model evaluator to record identity consent before the editorial approval.

Use the how-to method method

Translate the request into an input, a reversible action, a checkpoint, and a finished handoff. Practice on a duplicate or non-sensitive sample, preserve the original, and stop when authorization, account access, safety, or factual uncertainty appears. For this query, write selection criteria, verify licenses and identity rights, and compare candidates on the same evidence. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The how-to-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. For the working record, preserve the source ledger, and ask the policy reviewer to record reversal cost 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. For this checkpoint, preserve the delivery checklist, and ask the source custodian to record control availability before the reversible handoff.

• Clarify the intended meaning For this checkpoint, preserve the reference set, and ask the production lead to record evidence freshness before the reversible handoff.
• Choose an authorized example In the decision log, preserve the source ledger, and ask the source custodian to record input provenance before the final sign-off.
• Name the evidence needed for the next decision In the decision log, preserve the brief version, and ask the production lead to record revision intent before the final sign-off.

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

The result should be reproducible from the written decisions while leaving product-specific buttons, limits, and account behavior to current official documentation rather than invented steps. 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 controlled test, preserve the review copy, and ask the policy reviewer to record claim scope before the controlled revision.