Fantasy Video: fantasy scene 34 - own category - orbit - photorealisti - SaaS B2B PM Tool

# Fantasy Video: fantasy scene 34 - own category - orbit - photorealisti - SaaS B2B PM Tool **Category:** Video Prompt → Fantasy | **Audience:** Professionals or practitioners using AI for fantasy tasks. | **Delivery:** Primary video platform/application **Job:** Improve the named business/performance outcome using a measurable, testable intervention. ## SOURCE INPUT Use this source brief as the authoritative task/scenario. Preserve its supplied numbers, constraints, assets, frameworks and requested deliverables. Separate facts from assumptions; never invent missing evidence. > Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims. > > > PROMPT FOR RUNWAY GEN-4 TURBO / SORA / LUMA: Scene: fantasy scene 34 - own category - orbit - photorealistic 8K - variant 447, Fantasy premium commercial for SaaS B2B PM Tool, photorealistic not CGI, Arri Alexa 65, overcast softbox environment, action rank #1 for 20 keywords, mood mysterious noir Camera: macro dolly slider 35mm f/2.8, focus pull at 2s Lighting: cinematic three-point large soft 12x12 diffusion 5600K + fill + rim kicker, volumetric haze, global illumination Duration: 8s 24fps 180° shutter, 3840x2160, 16:9 master + 9:16 vertical centered + 1:1 safe SHOT LIST: 0-2s establishing wide breathing, 2-4s reveal move start subject enters light shift focus pull, 4-6s hero macro detail thumbnail hold 1.5s, 6-8s outro pull back 20% headroom logo CTA clean freeze Negative: no morphing, no extra limbs, no text watermark, no flicker jitter, no AI wobble, no low-res blurry Audio: luxury tick 60bpm QA: Loop clean? Headroom? Flicker? Apple approved? > > ## CATEGORY-NATIVE PRODUCTION > Intent → Story/Action Strategy → Shot & Motion Design → Model Adapter → Failure Prevention → Variant Test → Platform Adaptation → QA. Translate the brief into production-ready instructions. Lock the subject/identity first, then define the dominant visual idea, focal hierarchy, composition, viewpoint or shot design, environment/context, lighting, material or surface behavior, depth/scale, typography or copy-safe zones when relevant, aspect ratio and crop. Preserve all supplied reference invariants. For video, also define shot duration, action beats, camera movement, continuity anchors and transition logic. Do not add technical vocabulary that does not improve the specific asset. > > ## MODEL ADAPTER > Adapt the production prompt to the requested model(s). Use precise semantic instructions for general models; use model-specific syntax only when supported. Never invent parameters or capabilities. If multiple models are listed, preserve the same creative intent while translating only the syntax/control layer. ## CREATIVE PRODUCTION SYSTEM **Workflow:** Creative intent → narrative/action → shot design → camera/motion → lighting/style → continuity → model adapter → failure prevention → variants → platform delivery → QA Translate the brief into observable production decisions: - subject/reference invariants - composition/hierarchy - category-native medium/style logic - lighting/material/graphic or motion behavior where relevant - perspective/scale/continuity where relevant - typography/text integrity when relevant - aspect ratio/crop and final-use requirements Do not add camera, cinematic, environmental or technical instructions that do not materially apply to this medium. **Model adapter** Target model(s): ChatGPT-4o, Claude 3.5, Gemini 1.5, Midjourney v6.1, Runway Gen-4, Sora. Keep creative intent model-neutral; adapt only supported syntax/capabilities. Never promise exact text, identity, geometry or motion behavior beyond what the model can reasonably deliver. **Failure prevention** Protect: action is physically coherent, shot continuity is maintained, camera movement is feasible, timing is explicit, platform format is usable. Also check identity/reference fidelity, accidental objects, contradictory perspective/scale, unusable crops and medium-inconsistent details. **Output contract** Return a production-ready prompt/plan with concrete visual decisions, constraints, negative/failure controls where useful, and a final-use QA checklist. ## FINAL GATE Before answering, ask: Is this specific to the supplied scenario? Is every important instruction actionable? Are assumptions labeled? Is the output genuinely usable? Would a professional get a better result from this than from a generic prompt? If not, revise the weakest part before delivering.