01Define the prompt refinement workflow behind sora 2 prompt optimizer
For Sora 2 Prompt Optimizer, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep model-specific prompts variants comparable instead of producing unrelated ideas. Preserve the original brief, identify one ambiguity or conflict, and revise a single instruction per pass. Enhancing or optimizing should make decisions more observable; it should not inflate prose, invent model parameters, or silently change the subject and intended outcome. Write the decision owner and intended handoff beside the brief so a search phrase cannot be mistaken for a verified product capability or an instruction that has already been executed. While evidence is current, preserve the handoff draft, and ask the identity reviewer to record source fidelity before the reversible handoff.
02Apply the model-specific prompts structure
Write a portable core prompt before adding any vendor or version vocabulary. Keep the subject, action, spatial relationship, shot order, continuity anchors, and end condition independent from a named model. Put model-specific controls in a separate dated note so an unsupported parameter cannot quietly become part of the creative brief. For “sora 2 prompt optimizer”, keep a visible distinction between required content, optional treatment, exclusions, and facts that need evidence. That structure gives controlled variants a stable baseline and lets a reviewer identify which instruction caused a material change. While evidence is current, preserve the delivery checklist, and ask the accessibility reviewer to record human approval before the reversible handoff.
03Prepare authorized inputs for general creative direction
This query calls for the intended medium, audience, purpose, authorized sources, subject, action, context, constraints, reviewer, and delivery condition. Turn broad or ambiguous words into observable choices. Define one outcome, order the important decisions, remove contradictions, and keep optional style language separate from required content. Record the source, permission, intended audience, protected details, and reviewer before testing language. The goal is a traceable creative proposal, not an assumption that a named platform, model, or workspace will perform the requested action. Before revision, preserve the decision history, and ask the policy reviewer to record source fidelity before the scope confirmation.
04Build controlled variants and observable acceptance checks
For this owner, the first review pass should make sora, optimizer observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. A refined version succeeds when it is shorter or clearer, retains required anchors, resolves the named ambiguity, and gives a reviewer a specific reason to prefer it. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. While evidence is current, preserve the claim inventory, and ask the delivery owner to record visible continuity before the acceptance review.
05Review authorization, safety, and changing product facts
Treat unclear product, entity, and platform references as questions. Do not invent capabilities, facts, identities, access terms, or production results to fill a gap in the query. The named third-party model or product requires dated first-party verification for identity, version, access, inputs, controls, limits, pricing, licensing, and output behavior; this page makes no comparison or SEELE availability claim. Treat every named model, competitor, access term, platform rule, identity use, commercial claim, and output specification as a dated evidence question. If authorization or first-party support is missing, keep the language editorial, stop the handoff, and record the unresolved gap instead of inventing a workaround. Before approval, preserve the claim inventory, and ask the channel editor to record camera logic before the workflow transfer.
06Approve a reversible prompt handoff
Confirm the exact provider, version, access surface, accepted inputs, controls, and output behavior against current first-party material before a test. A model name in a query is an evaluation target, not proof that SEELE or any other product currently exposes it. Before approving “sora 2 prompt optimizer”, check purpose, source rights, identity consent, factual support, continuity, disclosure, destination requirements, and the named review owner. Preserve the original brief and version notes. This handoff supplies authored guidance only and neither runs generation nor guarantees access, quality, speed, licensing, publishing, downloads, or outcomes. Before approval, preserve the authorization record, and ask the claims reviewer to record input provenance before the workflow transfer.