Define the planning job before choosing a product

Treat “scripts 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 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. In the decision log, preserve the evidence table, and ask the production lead to record visible continuity before the editorial approval.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve In the decision log, preserve the rights memo, and ask the source custodian to record identity consent before the editorial approval.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes In the decision log, preserve the reference set, and ask the source custodian to record format readiness before the editorial approval.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority In the decision log, preserve the delivery checklist, and ask the continuity editor to record evidence freshness before the editorial approval.

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. In the decision log, preserve the review copy, and ask the production lead to record disclosure clarity before the bounded test.

Apply the topic orientation boundary

Treat ambiguous or weakly related search language as a question to clarify. Do not turn it into a SEELE capability, endorsement, factual claim, or interactive workflow without evidence. Work from a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve. Review toward a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes. 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 rights memo, and ask the source custodian to record source fidelity before the scope confirmation.

• Clarify the intended meaning Before delivery, preserve the evidence table, and ask the production lead to record claim scope before the scope confirmation.
• Choose an authorized example Before delivery, preserve the input snapshot, and ask the delivery owner to record format readiness before the fallback decision.
• Name the evidence needed for the next decision Before delivery, preserve the control log, and ask the continuity editor to record human approval before the fallback decision.

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. At this stage, preserve the rights memo, and ask the rights reviewer to record format readiness before the evidence refresh.