Operating sequence

Build Prompt Collections for Review focus: shot contract, fact checker, reference integrity, and reversible handoff; keep collections evidence separate from prompt assumptions.

  1. 01

    Write the invariant shot intent first

    For Prompt Collections, 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 frame review; have the rights reviewer 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 collections evidence separate from prompt 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 annotated source board; have the post supervisor review camera intent; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep collections evidence separate from prompt 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 test worksheet; have the visual lead review visual hierarchy; 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 collections evidence separate from prompt assumptions.

    • Subject and action — record asset ledger, fact checker, delivery fit, and rights-cleared draft; keep collections evidence separate from prompt assumptions.
    • Framing and camera relationship — record versioned handoff, product specialist, claim support, and rights-cleared draft; keep collections evidence separate from prompt assumptions.
    • Beat order and end state — record rights record, channel owner, camera intent, and rights-cleared draft; keep collections evidence separate from prompt assumptions.
    • Continuity, sound intent, and exclusions — record input manifest, post supervisor, visual hierarchy, and reversible handoff; keep collections evidence separate from prompt 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 evidence ledger; have the product specialist review delivery fit; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep collections evidence separate from prompt 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 continuity sheet; have the channel owner review continuity; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep collections evidence separate from prompt 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 shot contract; have the rights reviewer review input fidelity; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep collections evidence separate from prompt assumptions.

  7. 07

    Build a specific test brief for prompt collections

    Start with a bounded text brief with visible constraints and an end state. 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 input manifest; have the editor review continuity; record the failed case as well as the accepted one; and do not advance it beyond a approved master until the named limitation is resolved. Keep collections evidence separate from prompt assumptions.

    • Primary query: prompt collections; test record: evidence ledger, prompt designer, message clarity, and source-preserving edit; keep collections evidence separate from prompt assumptions.
    • Editorial owner: keyword-expansion:0320; decision record: evidence ledger, prompt designer, visual hierarchy, and workflow decision; keep collections evidence separate from prompt assumptions.
    • Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: rights record, media owner, reference integrity, and dated decision; keep collections evidence separate from prompt assumptions.
  8. 08

    Separate topic fit from product proof

    A dated, user-provided competitor-gap export supports only the decision to cover “prompt collections.” 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 revision log; have the legal reviewer review continuity; record the failed case as well as the accepted one; and do not advance it beyond a workflow decision until the named limitation is resolved. Keep collections evidence separate from prompt assumptions.