Define the planning job before choosing a product

Treat “nano banana script” 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 script. 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. While evidence is current, preserve the continuity note, and ask the model evaluator to record revision intent before the production checkpoint.

• Input: the exact product, provider, version, region, account surface, production job, and verification date While evidence is current, preserve the claim inventory, and ask the rights reviewer to record input provenance before the production checkpoint.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps While evidence is current, preserve the authorization record, and ask the accessibility reviewer to record identity consent before the production checkpoint.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority While evidence is current, preserve the failure note, and ask the claims reviewer to record source fidelity before the production checkpoint.

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. While evidence is current, preserve the input snapshot, and ask the model evaluator to record control availability before the editorial approval.

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. At handoff, preserve the claim inventory, and ask the factual editor to record claim scope before the final sign-off.

• Confirm exact provider and version At handoff, preserve the continuity note, and ask the workflow owner to record identity consent before the final sign-off.
• Date every changing fact At handoff, preserve the review copy, and ask the source custodian to record claim scope before the scope confirmation.
• Keep observations separate from documentation At handoff, preserve the test fixture, and ask the production lead to record identity consent before the scope confirmation.

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 decision history, and ask the creative lead to record claim scope before the rights check.