Define the orientation job before choosing a product

Treat “story board 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 storyboard. 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 control log, and ask the production lead to record temporal order before the editorial approval.

• Input: an audience brief, supportable message, authorized references, beat list, visual constraints, and delivery target For a reversible workflow, preserve the input snapshot, and ask the source custodian to record camera logic before the editorial approval.
• Success: a traceable script or board in which each beat has a purpose, source, shot intention, continuity note, and review owner For a reversible workflow, preserve the brief version, and ask the accessibility reviewer to record human approval before the bounded test.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For a reversible workflow, preserve the source ledger, and ask the production lead to record failure conditions 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 claim inventory, and ask the continuity editor to record reversal cost before the editorial approval.

Apply the script and storyboard planning boundary

Templates and generated suggestions are proposals, not factual evidence or finished footage. Do not fabricate quotes, customer experience, product behavior, or rights to reference imagery. Work from an audience brief, supportable message, authorized references, beat list, visual constraints, and delivery target. Review toward a traceable script or board in which each beat has a purpose, source, shot intention, continuity note, and review owner. 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 failure note, and ask the production lead to record claim scope before the controlled revision.

• Map every beat to purpose and evidence At the next gate, preserve the authorization record, and ask the brand reviewer to record visible continuity before the controlled revision.
• Preserve source and identity rights At the next gate, preserve the decision history, and ask the accessibility reviewer to record disclosure clarity before the source comparison.
• Review continuity before visual polish At the next gate, preserve the handoff draft, and ask the rights 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. At this stage, preserve the input snapshot, and ask the production lead to record revision intent before the scope confirmation.