Operating sequence

Build Random Prompts for general video Review focus: camera plan, fact checker, motion coherence, and editorial approval; keep prompts evidence separate from random assumptions.

  1. 01

    Write the invariant shot intent first

    For Random Prompts, 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 shot contract; have the motion designer review revision control; 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 prompts evidence separate from random assumptions.

  2. 02

    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 continuity sheet; have the rights reviewer 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 prompts evidence separate from random assumptions.

  3. 03

    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 evidence ledger; have the legal reviewer 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 prompts evidence separate from random assumptions.

    • Subject and action — record acceptance matrix, technical reviewer, reference integrity, and versioned review; keep prompts evidence separate from random assumptions.
    • Framing and camera relationship — record input manifest, post supervisor, action readability, and workflow decision; keep prompts evidence separate from random assumptions.
    • Beat order and end state — record delivery checklist, art director, visual hierarchy, and versioned review; keep prompts evidence separate from random assumptions.
    • Continuity, sound intent, and exclusions — record versioned handoff, product specialist, continuity, and workflow decision; keep prompts evidence separate from random assumptions.
  4. 04

    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 test worksheet; have the producer review delivery fit; 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 prompts evidence separate from random assumptions.

  5. 05

    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 annotated source board; have the editor review identity consent; 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 prompts evidence separate from random assumptions.

  6. 06

    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 frame review; have the motion designer 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 prompts evidence separate from random assumptions.

  7. 07

    Build a specific test brief for random prompts

    Start with a rights-cleared representative source and a written acceptance 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 test worksheet; have the prompt designer review claim support; record the failed case as well as the accepted one; and do not advance it beyond a bounded experiment until the named limitation is resolved. Keep prompts evidence separate from random assumptions.

    • Primary query: random prompts; test record: shot contract, post supervisor, input fidelity, and editorial approval; keep prompts evidence separate from random assumptions.
    • Editorial owner: keyword-expansion:0191; decision record: input manifest, motion designer, reference integrity, and workflow decision; keep prompts evidence separate from random assumptions.
    • Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: test worksheet, editor, continuity, and release review; keep prompts evidence separate from random assumptions.
  8. 08

    Separate topic fit from product proof

    A dated, user-provided competitor-gap export supports only the decision to cover “random prompts.” 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 delivery checklist; have the motion designer review revision control; record the failed case as well as the accepted one; and do not advance it beyond a delivery package until the named limitation is resolved. Keep prompts evidence separate from random assumptions.