Define the planning job before choosing a product

Treat “katalist ai storyboard generator” 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 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. At this stage, preserve the delivery checklist, and ask the claims reviewer to record human approval before the source comparison.

• Input: the exact product, provider, version, region, account surface, production job, and verification date At this stage, preserve the reference set, and ask the channel editor to record source fidelity before the controlled revision.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps At this stage, preserve the rights memo, and ask the channel editor to record revision intent before the source comparison.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At this stage, preserve the evidence table, and ask the release approver to record camera logic before the source comparison.

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. At this stage, preserve the handoff draft, and ask the workflow owner to record source fidelity before the source comparison.

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 brief version, and ask the production lead to record disclosure clarity before the production checkpoint.

• Confirm exact provider and version Before delivery, preserve the source ledger, and ask the source custodian to record temporal order before the production checkpoint.
• Date every changing fact Before delivery, preserve the reference set, and ask the production lead to record human approval before the release review.
• Keep observations separate from documentation Before delivery, preserve the delivery checklist, and ask the source custodian to record format readiness before the release review.

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. For this checkpoint, preserve the evidence table, and ask the continuity editor to record disclosure clarity before the evidence refresh.