01Write the invariant shot intent first
For Nano Bana 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 acceptance matrix; have the channel owner review licensing; 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 prompts evidence separate from nano assumptions.
02Turn 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 input manifest; have the rights reviewer review revision control; 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 prompts evidence separate from nano assumptions.
03Layer 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 delivery checklist; have the editor review reference integrity; 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 prompts evidence separate from nano assumptions.
04Create 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 versioned handoff; have the visual lead 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 prompts evidence separate from nano assumptions.
05Review 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 rights record; have the legal reviewer review temporal stability; 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 prompts evidence separate from nano assumptions.
06Keep 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 decision memo; have the channel owner review continuity; 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 nano assumptions.
07Build a specific test brief for nano bana 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 annotated source board; have the brand reviewer review visual hierarchy; 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 prompts evidence separate from nano assumptions.
08Separate topic fit from product proof
A dated, user-provided competitor-gap export supports only the decision to cover “nano bana 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 camera plan; have the channel owner review reference integrity; record the failed case as well as the accepted one; and do not advance it beyond a shot approval until the named limitation is resolved. Keep prompts evidence separate from nano assumptions.