Operating sequence
Build Imagefx Prompts for general Review focus: annotated source board, channel owner, source rights, and approved master; keep prompts evidence separate from imagefx assumptions.
- 01
Write the invariant shot intent first
For Imagefx 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 annotated source board; have the post supervisor review temporal stability; 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 imagefx assumptions.
- 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 frame review; have the rights reviewer review message clarity; 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 imagefx assumptions.
- 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 revision log; have the legal reviewer review reference integrity; 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 imagefx assumptions.
- Subject and action — record delivery checklist, art director, licensing, and delivery package; keep prompts evidence separate from imagefx assumptions.
- Framing and camera relationship — record camera plan, media owner, identity consent, and delivery package; keep prompts evidence separate from imagefx assumptions.
- Beat order and end state — record acceptance matrix, technical reviewer, delivery fit, and delivery package; keep prompts evidence separate from imagefx assumptions.
- Continuity, sound intent, and exclusions — record decision memo, technical reviewer, visual hierarchy, and delivery package; keep prompts evidence separate from imagefx assumptions.
- 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 prompt brief; have the editor review continuity; record the failed case as well as the accepted one; and do not advance it beyond a reversible handoff until the named limitation is resolved. Keep prompts evidence separate from imagefx assumptions.
- 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 shot contract; have the rights reviewer review delivery fit; record the failed case as well as the accepted one; and do not advance it beyond a reversible handoff until the named limitation is resolved. Keep prompts evidence separate from imagefx assumptions.
- 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 continuity sheet; have the channel owner review action readability; record the failed case as well as the accepted one; and do not advance it beyond a reversible handoff until the named limitation is resolved. Keep prompts evidence separate from imagefx assumptions.
- 07
Build a specific test brief for imagefx 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 asset ledger; have the editor review continuity; 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 prompts evidence separate from imagefx assumptions.
- Primary query: imagefx prompts; test record: revision log, post supervisor, continuity, and production checkpoint; keep prompts evidence separate from imagefx assumptions.
- Editorial owner: keyword-expansion:0463; decision record: revision log, motion designer, message clarity, and workflow decision; keep prompts evidence separate from imagefx assumptions.
- Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: frame review, product specialist, continuity, and workflow decision; keep prompts evidence separate from imagefx assumptions.
- 08
Separate topic fit from product proof
A dated, user-provided competitor-gap export supports only the decision to cover “imagefx 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 asset ledger; have the media owner review licensing; record the failed case as well as the accepted one; and do not advance it beyond a production checkpoint until the named limitation is resolved. Keep prompts evidence separate from imagefx assumptions.