Turn Prompt Video into a reviewable shot contract.

Write the invariant shot intent first

For Prompt Video, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep general video prompts variants comparable instead of producing unrelated ideas. For this section 1, save a test worksheet; have the rights reviewer review claim support; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

Turn the topic into a repeatable method

Move from definition to a small practice sequence, then review the result against explicit craft, rights, and delivery checks. Keep vendor-specific behavior outside the method unless a source verifies it. For this section 2, save a revision log; have the editor review camera intent; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

Layer camera, timing, continuity, and sound

Add framing and camera movement only when they support the action. Mark temporal beats, preserve identity and environment anchors, describe sound as intent rather than a guaranteed feature, and name artifacts or changes to avoid. For this section 3, save a frame review; have the product specialist review visual hierarchy; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

• Subject and action — record prompt brief, media owner, editability, and approved master; keep video evidence separate from prompt assumptions.
• Framing and camera relationship — record evidence ledger, technical reviewer, continuity, and approved master; keep video evidence separate from prompt assumptions.
• Beat order and end state — record continuity sheet, fact checker, claim support, and approved master; keep video evidence separate from prompt assumptions.
• Continuity, sound intent, and exclusions — record annotated source board, prompt designer, action readability, and approved master; keep video evidence separate from prompt assumptions.

Create controlled prompt variants

Change one meaningful dimension per version, such as shot size, movement, pacing, or performance intensity. Label the hypothesis for each variant so review can identify which instruction caused the difference. For this section 4, save a shot contract; have the product specialist review motion coherence; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

Review the output without inventing model controls

Check whether the requested action reads clearly, the camera supports the beat, references remain coherent, and the ending is usable. A prompt template does not prove that any named model, duration, audio mode, or parameter is available. For this section 5, save a prompt brief; have the channel owner review message clarity; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

Keep the evidence ledger attached to the decision

Partial evidence was supplied, but it does not establish product support or a complete capability, customer, or performance claim. Record the source, verification date, claim scope, unresolved gap, and the decision that the evidence can support. Search demand must never be reused as capability proof. For this section 6, save a evidence ledger; have the post supervisor review input fidelity; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

Build a specific test brief for prompt video

Start with an authorized representative clip and its delivery brief. Define one observable change, protected details, a stopping rule, and the named reviewer. The intended output is a reusable prompt contract with controlled variants. Test one variable per version, preserve the source and settings, and compare results at the actual delivery size instead of choosing from an unrecorded impression. For this topic test, save a evidence ledger; have the technical reviewer review temporal stability; record the failed case as well as the accepted one; and do not advance it beyond a reproducible test until the named limitation is resolved. Keep video evidence separate from prompt assumptions.

• Primary query: prompt video; test record: versioned handoff, channel owner, delivery fit, and delivery package; keep video evidence separate from prompt assumptions.
• Editorial owner: keyword-expansion:0225; decision record: versioned handoff, technical reviewer, input fidelity, and source-preserving edit; keep video evidence separate from prompt assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: continuity sheet, brand reviewer, claim support, and reproducible test; keep video evidence separate from prompt assumptions.

Separate topic fit from product proof

A dated, user-provided competitor-gap export supports only the decision to cover “prompt video.” It does not prove audience demand, SEELE capability, third-party behavior, commercial value, or a likely outcome. Verify product-specific statements against current first-party documentation and a recorded representative test. For this source review, save a shot contract; have the visual lead review claim support; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep video evidence separate from prompt assumptions.