Turn Nano Prompts into a reviewable shot contract.

Write the invariant shot intent first

For Nano 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 test worksheet; have the creative producer review licensing; 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 prompts evidence separate from nano 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 producer review identity consent; 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 prompts evidence separate from nano 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 brand reviewer review editability; 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 prompts evidence separate from nano assumptions.

• Subject and action — record asset ledger, product specialist, input fidelity, and dated decision; keep prompts evidence separate from nano assumptions.
• Framing and camera relationship — record versioned handoff, brand reviewer, identity consent, and dated decision; keep prompts evidence separate from nano assumptions.
• Beat order and end state — record rights record, motion designer, delivery fit, and dated decision; keep prompts evidence separate from nano assumptions.
• Continuity, sound intent, and exclusions — record input manifest, visual lead, claim support, and dated decision; keep prompts evidence separate from nano 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 brand reviewer review action readability; 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 prompts evidence separate from nano 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 motion designer review temporal stability; 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 prompts evidence separate from nano 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 visual lead review revision control; 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 prompts evidence separate from nano assumptions.

Build a specific test brief for nano 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 evidence ledger; have the prompt designer review continuity; record the failed case as well as the accepted one; and do not advance it beyond a release review until the named limitation is resolved. Keep prompts evidence separate from nano assumptions.

• Primary query: nano prompts; test record: evidence ledger, producer, motion coherence, and reproducible test; keep prompts evidence separate from nano assumptions.
• Editorial owner: keyword-expansion:0724; decision record: evidence ledger, producer, camera intent, and source-preserving edit; keep prompts evidence separate from nano assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: rights record, fact checker, delivery fit, and source-preserving edit; keep prompts evidence separate from nano assumptions.

Separate topic fit from product proof

A dated, user-provided competitor-gap export supports only the decision to cover “nano 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 shot contract; have the fact checker review source rights; 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 nano assumptions.