Turn Nano Prompt into a reviewable shot contract.

Write the invariant shot intent first

For Nano Prompt, 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 rights record; have the rights reviewer review reference integrity; 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 prompt 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 decision memo; have the post supervisor 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 prompt 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 asset ledger; have the art director review visual hierarchy; 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 prompt evidence separate from nano assumptions.

• Subject and action — record versioned handoff, prompt designer, camera intent, and reversible handoff; keep prompt evidence separate from nano assumptions.
• Framing and camera relationship — record asset ledger, legal reviewer, continuity, and reversible handoff; keep prompt evidence separate from nano assumptions.
• Beat order and end state — record decision memo, visual lead, delivery fit, and reversible handoff; keep prompt evidence separate from nano assumptions.
• Continuity, sound intent, and exclusions — record acceptance matrix, visual lead, message clarity, and reproducible test; keep prompt 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 camera plan; have the channel owner 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 prompt 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 acceptance matrix; have the post supervisor 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 prompt 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 input manifest; have the editor review motion coherence; 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 prompt evidence separate from nano assumptions.

Build a specific test brief for nano prompt

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 shot contract; have the legal reviewer review source rights; record the failed case as well as the accepted one; and do not advance it beyond a dated decision until the named limitation is resolved. Keep prompt evidence separate from nano assumptions.

• Primary query: nano prompt; test record: prompt brief, legal reviewer, licensing, and release review; keep prompt evidence separate from nano assumptions.
• Editorial owner: keyword-expansion:0723; decision record: delivery checklist, rights reviewer, editability, and approved master; keep prompt evidence separate from nano assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: decision memo, producer, temporal stability, and rights-cleared draft; keep prompt 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 prompt.” 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 evidence ledger; have the media owner review delivery fit; 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 prompt evidence separate from nano assumptions.