Add reference video input analysis workflow
This commit is contained in:
calesthio
@@ -22,6 +22,31 @@ Animation proposals have a unique dimension: **animation mode selection**. Unlik
|
||||
|
||||
## Process
|
||||
|
||||
### Step 0: Check for Reference Video Context
|
||||
|
||||
Before starting proposal work, check if a VideoAnalysisBrief exists for this project.
|
||||
|
||||
**When a VideoAnalysisBrief is present — Reference-Aware Animation Concept Design:**
|
||||
|
||||
**HARD RULE: No carbon copies.** Each concept option MUST:
|
||||
1. Name at least ONE animation element it keeps from the reference (pacing, motion style, narrative structure)
|
||||
2. Name at least ONE element it changes (animation mode, visual identity, topic angle)
|
||||
3. Explain WHY the change makes the output more engaging or clearer
|
||||
|
||||
**Animation differentiation patterns:**
|
||||
|
||||
| Pattern | Example |
|
||||
|---------|---------|
|
||||
| **Same topic, different animation mode** | Reference: stock footage → Ours: Manim mathematical visualization |
|
||||
| **Same style, different complexity** | Reference: simple diagrams → Ours: progressive build with layers |
|
||||
| **Same pacing, different visual identity** | Reference: corporate blue → Ours: vibrant neon-on-black |
|
||||
| **Same narrative, different interactivity** | Reference: linear → Ours: data-driven with animated charts |
|
||||
|
||||
**Mandatory Sample Protocol:** After concept approval, produce a 10-15 second sample
|
||||
to validate the animation style before full production.
|
||||
|
||||
**When no VideoAnalysisBrief is present:** Skip this step and proceed normally.
|
||||
|
||||
### Step 1: Absorb the Research (or Direct Brief)
|
||||
|
||||
**If a `research_brief` artifact exists:** Read it thoroughly. Extract:
|
||||
|
||||
@@ -18,6 +18,40 @@ Animation videos differ from general explainers: the research must cover both **
|
||||
|
||||
## Process
|
||||
|
||||
### Step 0: Check for Reference Video Context
|
||||
|
||||
Before starting research, check if a VideoAnalysisBrief exists for this project. If it
|
||||
does, this is a reference-driven production — the user provided a video they want to
|
||||
riff on.
|
||||
|
||||
**When a VideoAnalysisBrief is present:**
|
||||
|
||||
1. Read it thoroughly. Extract:
|
||||
- `content_analysis.topics` — research these topics for accuracy
|
||||
- `content_analysis.key_claims` — verify these claims via web search
|
||||
- `style_profile` — note the animation style (motion type, color palette, transitions)
|
||||
- `structure_analysis.pacing_profile` — understand the rhythm
|
||||
- `replication_guidance.creative_differentiation_seeds` — these are your concept seeds
|
||||
- `replication_guidance.key_elements_to_replicate` — preserve these in proposals
|
||||
|
||||
2. Your research focus SHIFTS:
|
||||
- Standard research: "What topic + animation technique fits?"
|
||||
- Reference-driven research: "What animation approach would DIFFERENTIATE us from the
|
||||
reference while keeping the elements the user loved?" + "What animation techniques
|
||||
exist for this topic that the reference DIDN'T use?"
|
||||
|
||||
3. In the research_brief, add a `reference_context` section:
|
||||
- The reference's animation style and technique
|
||||
- What animation modes it used (motion graphics, manim, illustrative, etc.)
|
||||
- Alternative animation approaches we could try instead
|
||||
- What the reference did well vs. where we can improve
|
||||
|
||||
4. The `angles_discovered` should explicitly position against the reference:
|
||||
- "The reference used X animation style. We could try Y which is [more engaging/clearer/
|
||||
more novel] because [technique research finding]."
|
||||
|
||||
**When no VideoAnalysisBrief is present:** Skip this step and proceed normally.
|
||||
|
||||
### Step 1: Scope the Research
|
||||
|
||||
Before searching anything, establish boundaries:
|
||||
|
||||
@@ -20,6 +20,32 @@ You are the **Proposal Director** for a cinematic video (trailers, brand films,
|
||||
|
||||
## Process
|
||||
|
||||
### Step 0: Check for Reference Video Context
|
||||
|
||||
Before starting proposal work, check if a VideoAnalysisBrief exists for this project.
|
||||
|
||||
**When a VideoAnalysisBrief is present — Reference-Aware Cinematic Concept Design:**
|
||||
|
||||
**HARD RULE: No carbon copies.** Each concept option MUST:
|
||||
1. Name at least ONE cinematic element it keeps from the reference (mood, pacing, color palette, shot language)
|
||||
2. Name at least ONE element it changes (emotional arc, visual treatment, subject matter, sound design)
|
||||
3. Explain WHY the change creates a different emotional impact
|
||||
|
||||
**Cinematic differentiation patterns:**
|
||||
|
||||
| Pattern | Example |
|
||||
|---------|---------|
|
||||
| **Same mood, different subject** | Reference: dark sci-fi mood → Ours: same darkness applied to deep ocean |
|
||||
| **Same subject, different emotional arc** | Reference: tension→reveal → Ours: wonder→scale |
|
||||
| **Same pacing, different visual language** | Reference: handheld raw → Ours: locked-off geometric |
|
||||
| **Same color world, different lighting** | Reference: warm golden hour → Ours: warm but tungsten/interior |
|
||||
|
||||
**Mandatory Sample Protocol:** After concept approval, produce a 10-15 second cinematic
|
||||
sample BEFORE full production. This is critical for cinematic work — mood mismatches are
|
||||
expensive to fix downstream. Present with visual + audio + music.
|
||||
|
||||
**When no VideoAnalysisBrief is present:** Skip this step and proceed normally.
|
||||
|
||||
### Step 1: Absorb the Research
|
||||
|
||||
Read the `research_brief` thoroughly. Extract:
|
||||
|
||||
@@ -18,6 +18,40 @@ Unlike explainer research (which focuses on facts, data, and content gaps), cine
|
||||
|
||||
## Process
|
||||
|
||||
### Step 0: Check for Reference Video Context
|
||||
|
||||
Before starting research, check if a VideoAnalysisBrief exists for this project. If it
|
||||
does, this is a reference-driven production — the user provided a video they want to
|
||||
riff on.
|
||||
|
||||
**When a VideoAnalysisBrief is present:**
|
||||
|
||||
1. Read it thoroughly. Extract:
|
||||
- `content_analysis.topics` — research these topics for accuracy
|
||||
- `content_analysis.key_claims` — verify these claims via web search
|
||||
- `style_profile` — note the cinematic language (color palette, camera movements, lighting)
|
||||
- `structure_analysis.scenes` — understand the shot language and emotional arc
|
||||
- `replication_guidance.creative_differentiation_seeds` — these are your concept seeds
|
||||
- `replication_guidance.key_elements_to_replicate` — preserve these in proposals
|
||||
|
||||
2. Your research focus SHIFTS:
|
||||
- Standard research: "What visual/emotional language fits this subject?"
|
||||
- Reference-driven research: "What cinematic approach would DIFFERENTIATE us from the
|
||||
reference while keeping the elements the user loved?" + "What mood/tone territory
|
||||
is adjacent but unexplored?"
|
||||
|
||||
3. In the research_brief, add a `reference_context` section:
|
||||
- The reference's cinematic language (shot types, pacing, color palette)
|
||||
- What emotional territory it occupies
|
||||
- Adjacent emotional territories we could explore instead
|
||||
- How the reference's visual approach could be evolved or reinterpreted
|
||||
|
||||
4. The `angles_discovered` should explicitly position against the reference:
|
||||
- "The reference uses X mood/palette/pacing. We could try Y which creates
|
||||
[different emotional impact] because [research finding]."
|
||||
|
||||
**When no VideoAnalysisBrief is present:** Skip this step and proceed normally.
|
||||
|
||||
### Step 1: Classify the Brief
|
||||
|
||||
Before searching, extract from the user's request:
|
||||
|
||||
@@ -22,6 +22,36 @@ Think of yourself as a creative agency pitching to a client: you present concept
|
||||
|
||||
## Process
|
||||
|
||||
### Step 0: Check for Reference Video Context
|
||||
|
||||
Before starting proposal work, check if a VideoAnalysisBrief exists for this project.
|
||||
|
||||
**When a VideoAnalysisBrief is present — Reference-Aware Concept Design:**
|
||||
|
||||
**HARD RULE: No carbon copies.** Each concept option MUST:
|
||||
1. Name at least ONE element it keeps from the reference (pacing, structure, tone, hook style)
|
||||
2. Name at least ONE element it changes (topic angle, visual treatment, narration approach)
|
||||
3. Explain WHY the change makes the output better, not just different
|
||||
|
||||
**Differentiation patterns:**
|
||||
|
||||
| Pattern | Example |
|
||||
|---------|---------|
|
||||
| **Same structure, different subject** | Reference: "How black holes work" → Ours: "How neutron stars work" with same pacing |
|
||||
| **Same subject, different angle** | Reference: "Kubernetes explained" → Ours: "Kubernetes from a security engineer's POV" |
|
||||
| **Same tone, different visual treatment** | Reference: stock footage + voiceover → Ours: animated motion graphics + voiceover |
|
||||
| **Same content, different platform** | Reference: 10-min YouTube → Ours: 60-sec Shorts version with faster pacing |
|
||||
| **Counter-take** | Reference: "Why AI will replace jobs" → Ours: "Why AI won't replace YOUR job" |
|
||||
|
||||
**Mandatory Sample Protocol:** After the user approves a concept, BEFORE entering the
|
||||
script stage, produce a 10-15 second sample:
|
||||
1. The opening hook (first 5-7 seconds) + one representative middle scene
|
||||
2. Actual TTS voice, actual visual style, music bed snippet
|
||||
3. Present with: "Here's a preview. Does this feel right?"
|
||||
4. Iterate until approved, then proceed to full production
|
||||
|
||||
**When no VideoAnalysisBrief is present:** Skip this step and proceed normally.
|
||||
|
||||
### Step 1: Absorb the Research
|
||||
|
||||
Read the `research_brief` thoroughly. Extract:
|
||||
|
||||
@@ -18,6 +18,38 @@ This stage is what separates an OpenMontage video from generic AI slop. Without
|
||||
|
||||
## Process
|
||||
|
||||
### Step 0: Check for Reference Video Context
|
||||
|
||||
Before starting research, check if a VideoAnalysisBrief exists for this project. If it
|
||||
does, this is a reference-driven production — the user provided a video they want to
|
||||
riff on.
|
||||
|
||||
**When a VideoAnalysisBrief is present:**
|
||||
|
||||
1. Read it thoroughly. Extract:
|
||||
- `content_analysis.topics` — research these topics for accuracy
|
||||
- `content_analysis.key_claims` — verify these claims via web search
|
||||
- `style_profile` — note this for the proposal stage (do not research style)
|
||||
- `replication_guidance.creative_differentiation_seeds` — these are your concept seeds
|
||||
- `replication_guidance.key_elements_to_replicate` — preserve these in proposals
|
||||
|
||||
2. Your research focus SHIFTS:
|
||||
- Standard research: "What is interesting about this topic?"
|
||||
- Reference-driven research: "What is interesting about this topic that the
|
||||
reference video DIDN'T cover?" + "What would make our version DIFFERENT and BETTER?"
|
||||
|
||||
3. In the research_brief, add a `reference_context` section:
|
||||
- What the reference covered
|
||||
- What it missed (your differentiation opportunity)
|
||||
- What claims it made that you can verify or update
|
||||
- How the landscape has changed since the reference was published
|
||||
|
||||
4. The `angles_discovered` should explicitly position against the reference:
|
||||
- "The reference took angle X. We could take angle Y which is [fresher/deeper/more
|
||||
surprising] because [research finding]."
|
||||
|
||||
**When no VideoAnalysisBrief is present:** Skip this step and proceed normally.
|
||||
|
||||
### Step 1: Scope the Research
|
||||
|
||||
Before searching anything, establish boundaries:
|
||||
|
||||
Reference in New Issue
Block a user