Define the planning job before choosing a product

Treat “sora 2 storyboards” as a production-planning 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 named model or platform. 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 delivery, preserve the source ledger, and ask the production lead to record claim scope before the rights check.

• Input: the exact product, provider, version, region, account surface, production job, and verification date Before delivery, preserve the brief version, and ask the accessibility reviewer to record visible continuity before the rights check.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps Before delivery, preserve the input snapshot, and ask the source custodian to record evidence freshness before the rights check.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before delivery, preserve the control log, and ask the production lead to record failure conditions before the rights check.

Use the planning and scripting method

Begin with audience, purpose, source material, key message, sequence, and delivery condition. Draft the smallest useful outline, map each beat to evidence or an authorized asset, then revise structure before polishing language or imagining generated footage. For this query, turn the idea into a brief, ordered beats, review ownership, and a delivery contract. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The planning-scripting 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 delivery, preserve the authorization record, and ask the delivery owner to record visible continuity before the workflow transfer.

Apply the named platform or model facts boundary

Do not infer SEELE support, model access, quality, legitimacy, censorship, ownership, API behavior, or compatibility from the query. Verify first-party documentation and direct observations on the use date. Work from the exact product, provider, version, region, account surface, production job, and verification date. Review toward a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps. 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. Before delivery, preserve the reference set, and ask the accessibility reviewer to record revision intent before the source comparison.

• Confirm exact provider and version Before delivery, preserve the delivery checklist, and ask the production lead to record visible continuity before the source comparison.
• Date every changing fact Before delivery, preserve the brief version, and ask the accessibility reviewer to record reversal cost before the production checkpoint.
• Keep observations separate from documentation Before delivery, preserve the source ledger, and ask the production lead to record format readiness before the production checkpoint.

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

The handoff should let a reviewer trace every beat to its source, see what remains a creative proposal, and identify which script, board, transcript, or description decision needs approval next. 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 approval, preserve the test fixture, and ask the creative lead to record reversal cost before the workflow transfer.