Define the orientation job before choosing a product

Treat “ai쇼츠” 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. For a reversible workflow, preserve the test fixture, and ask the channel editor to record revision intent before the bounded test.

• Input: authorized media, the intended account and destination, current platform rules, disclosure needs, and a named publisher For a reversible workflow, preserve the review copy, and ask the claims reviewer to record visible continuity before the bounded test.
• Success: a channel-ready handoff whose captions, links, claims, identities, commerce context, and synthetic-media disclosure have been reviewed For a reversible workflow, preserve the handoff draft, and ask the brand reviewer to record disclosure clarity before the bounded test.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For a reversible workflow, preserve the decision history, and ask the release approver to record camera logic before the bounded test.

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. For a reversible workflow, preserve the rights memo, and ask the identity reviewer to record format readiness before the bounded test.

Apply the social and publishing policy boundary

Do not promise reach, approval, monetization, shop-link availability, or automatic publishing. Platform interface and policy facts must be checked at the time of handoff. Work from authorized media, the intended account and destination, current platform rules, disclosure needs, and a named publisher. Review toward a channel-ready handoff whose captions, links, claims, identities, commerce context, and synthetic-media disclosure have been reviewed. 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 handoff, preserve the input snapshot, and ask the release approver to record identity consent before the editorial approval.

• Verify current channel policy At handoff, preserve the control log, and ask the brand reviewer to record input provenance before the editorial approval.
• Review claims and disclosure At handoff, preserve the rights memo, and ask the factual editor to record camera logic before the editorial approval.
• Keep publishing with an authorized account owner At handoff, preserve the evidence table, and ask the workflow owner to record temporal order 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. In the decision log, preserve the failure note, and ask the workflow owner to record failure conditions before the acceptance review.