Orion vault — clean initial history

Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on
2026-10-01. Deliberately orphaned: prior history contained a plaintext
password and stays local-only on branch archive/pre-boilerplate-history.
Secrets and live Hermes state are gitignored.

3. Resources/Research/prompts/Prompt - 2d Animation.md

@@ -0,0 +1,271 @@
+### What I'd use locally
+
+If you're running **Qwen3.8 Flash locally**, I'd actually keep it for the **planning/director role**.
+
+Your pipeline would look roughly like:
+
+**Qwen3.8 Flash**  
+→ transcript analysis  
+→ characters  
+→ storyboard  
+→ shot prompts  
+→ asset list
+
+**Image model**  
+→ character sheets  
+→ backgrounds  
+→ props
+
+**Video/animation model**  
+→ animate each shot
+
+**FFmpeg / editing software**  
+→ assemble shots + narration + music + captions
+
+The key is that you **don't need one giant model to do everything**.
+
+If your laptop is the Framework machine you've been using for your local AI setup, the exact model choice depends heavily on your GPU/RAM. If you're **CPU-only or using integrated graphics**, I'd approach this very differently than if you have an NVIDIA GPU.
+
+If you tell me **your exact Framework specs (CPU, RAM, and GPU—if any)**, I can give you a specific local stack—**model by model—and tell you which parts Qwen3.8 Flash should handle versus which model should generate the actual 2D animation.**
+
+
+
+```
+You are an expert 2D cutout animation director and storyboard artist.
+
+I already have a completed narration transcript. Your job is to convert the transcript into a simple, AI-friendly 2D cutout animation plan.
+
+IMPORTANT:  
+Do NOT rewrite the narration.  
+Do NOT add unnecessary dialogue.  
+Do NOT create complicated animation.  
+Do NOT use realistic 3D animation.  
+Do NOT use anime.  
+Do NOT use detailed frame-by-frame animation.
+
+ANIMATION STYLE:
+
+- Simple 2D cutout/vector animation
+    
+- Flat colors
+    
+- Clean, minimal shapes
+    
+- Simple characters with recognizable silhouettes
+    
+- Simple facial expressions
+    
+- Characters constructed from reusable pieces: head, torso, arms, hands, legs
+    
+- Limited animation
+    
+- Characters can slide, walk, point, turn, gesture, nod, shake their head, sit, stand, or change facial expressions
+    
+- Reuse the same character designs throughout the entire video
+    
+- Reuse backgrounds whenever possible
+    
+- Use simple props and icons
+    
+- Use camera pans, zooms, and cuts to create visual interest
+    
+- Avoid complex physics, crowds, detailed environments, and complicated interactions
+    
+- Keep every shot easy for an AI image/video generation system to reproduce consistently
+    
+
+VISUAL PRIORITY:
+
+Narration > visual clarity > animation complexity.
+
+The visuals should support what the narrator is saying rather than trying to literally animate every word.
+
+CHARACTER CONSISTENCY:
+
+Create a small cast of recurring characters.
+
+For each character define:
+
+- Character name
+    
+- Age range
+    
+- Gender presentation if relevant
+    
+- Body shape
+    
+- Hair
+    
+- Clothing
+    
+- Main colors
+    
+- Distinguishing features
+    
+- Default facial expression
+    
+- Personality conveyed visually
+    
+
+Once a character is defined, NEVER redesign that character later in the video.
+
+BACKGROUND CONSISTENCY:
+
+Use a small number of reusable locations.
+
+For each location define:
+
+- Location name
+    
+- Basic layout
+    
+- Major objects
+    
+- Color/style
+    
+- Important recurring props
+    
+
+SHOT DESIGN:
+
+Break the transcript into individual shots.
+
+For every shot provide:
+
+1. Shot number
+    
+2. Transcript section being illustrated
+    
+3. Estimated duration
+    
+4. Location/background
+    
+5. Characters present
+    
+6. Character poses
+    
+7. Character actions
+    
+8. Facial expressions
+    
+9. Props
+    
+10. Camera movement
+    
+11. On-screen text, if needed
+    
+12. Transition from previous shot
+    
+13. Exact image-generation prompt
+    
+14. Exact animation/video-generation prompt
+    
+
+Keep individual shots visually simple.
+
+Prefer shots that can be generated using one static image plus limited motion.
+
+Whenever possible, use:
+
+- Character movement
+    
+- Camera movement
+    
+- Object movement
+    
+- Simple transitions
+    
+
+instead of complex animation.
+
+SHOT COMPLEXITY RULE:
+
+Every shot should receive a complexity rating from 1–5.
+
+1 = almost completely static  
+2 = one simple movement  
+3 = several simple movements  
+4 = moderately complex  
+5 = complex
+
+Try to keep at least 80% of the shots at complexity 1–3.
+
+If a shot would be complexity 4–5, redesign it into multiple simpler shots.
+
+AI GENERATION RULE:
+
+Design every shot so that an AI image/video model has the highest possible chance of maintaining character consistency.
+
+Avoid:
+
+- Multiple characters physically interacting
+    
+- Hands touching complicated objects
+    
+- Characters holding many objects
+    
+- Rapid movement
+    
+- Large crowds
+    
+- Complex camera movements
+    
+- Detailed backgrounds
+    
+- Multiple simultaneous actions
+    
+- Tiny text inside generated images
+    
+
+Instead, use separate shots.
+
+OUTPUT STRUCTURE:
+
+FIRST:  
+Give me the overall visual style guide.
+
+SECOND:  
+Give me the reusable character designs.
+
+THIRD:  
+Give me the reusable background/location designs.
+
+FOURTH:  
+Create the complete shot list in a table.
+
+FIFTH:  
+Provide the image-generation prompts for every shot.
+
+SIXTH:  
+Provide the animation/video-generation prompts for every shot.
+
+SEVENTH:  
+Provide a list of reusable assets that should only be generated once, including:
+
+- Characters
+    
+- Backgrounds
+  
+    
+- Props
+    
+- Icons
+    
+- Logos
+    
+
+EIGHTH:  
+Provide a recommended production workflow explaining exactly which assets should be generated first and how they should be reused across the video.
+
+VERY IMPORTANT:
+
+Do not attempt to make the animation visually impressive through complexity.
+
+Make it look intentionally simple, clean, consistent, and professional.
+
+The goal is a style that a local AI pipeline can realistically produce repeatedly without character drift or excessive rendering requirements.
+
+Here is the transcript:
+
+[PASTE TRANSCRIPT HERE]
+```