169 lines
4.7 KiB
Markdown
169 lines
4.7 KiB
Markdown
# Video Workbench Context Handoff
|
|
|
|
This document preserves the working agreements for Video Workbench so future Codex sessions do not depend on copied chat history.
|
|
|
|
## Confirmed Architecture
|
|
|
|
```text
|
|
Knowledge Vault = source archive and model/essay library
|
|
Writing Workbench = deep article production workspace
|
|
Video Workbench = public-facing dimensional video output workspace
|
|
CCPE System = actor, skill, model, and runtime factory
|
|
```
|
|
|
|
Video Workbench is a sibling of Writing Workbench. It should not be folded into article production because the target output, rhythm, assets, and evaluation criteria are different.
|
|
|
|
Video Workbench keeps local video production records. It does not own canonical prompts, agent definitions, reusable automation source code, or production/business agent implementation for deployable systems.
|
|
|
|
## User's Dimensional Output Workflow
|
|
|
|
The user's deep essays are often 7,000 to 50,000 Chinese characters. Direct decompression into public form can multiply the text volume, which does not fit current public reading habits.
|
|
|
|
The user's method:
|
|
|
|
```text
|
|
Extract one or two points from a deep article or model.
|
|
Connect them to a public-facing concern.
|
|
Produce a video usually under 10 minutes.
|
|
Use about 220 Chinese characters per minute as the narration budget.
|
|
```
|
|
|
|
The previous single-agent actor was named `强哥的徒弟`. Video Workbench should preserve the workflow but move toward file-based, agentic production.
|
|
|
|
## Workflow Stages
|
|
|
|
### Stage 0: Series Architecture
|
|
|
|
Decide whether the video belongs to a series or is standalone.
|
|
|
|
Inputs usually include:
|
|
|
|
- `knowledge-vault/rules` model documents
|
|
- `knowledge-vault/sayings` essay originals
|
|
- selected source material
|
|
|
|
Outputs:
|
|
|
|
- series plan, if any
|
|
- episode split
|
|
- target duration
|
|
- word budget
|
|
- selected source map
|
|
|
|
### Stage 1: Angle Proposals
|
|
|
|
Find three distinct entry angles.
|
|
|
|
Output style:
|
|
|
|
```text
|
|
EP.01 [temporary episode name] - angle proposal
|
|
```
|
|
|
|
The user selects the angle.
|
|
|
|
### Stage 2: Tone And Outline
|
|
|
|
Produce the video outline:
|
|
|
|
- framing and positioning
|
|
- core thought anchor
|
|
- governing metaphor
|
|
- global visual style constraints
|
|
- Chinese style description
|
|
- English Global Prompt parameters
|
|
- narration/writing protocol
|
|
|
|
### Stage 3: Storyboard Logic
|
|
|
|
Produce storyboard logic with time and word budget.
|
|
|
|
Example:
|
|
|
|
```text
|
|
Shot 1 [Puzzle Introduction]: 30 seconds / about 110 Chinese characters.
|
|
Shot 2 [Deep Dive]: 90 seconds / about 330 Chinese characters.
|
|
```
|
|
|
|
### Stage 4: Shot Deep Production
|
|
|
|
For each shot, produce:
|
|
|
|
- page or screen visual plan
|
|
- image generation prompt
|
|
- voiceover script
|
|
- design subtext
|
|
- transition notes
|
|
|
|
### Stage 5: Assets
|
|
|
|
Generate or collect:
|
|
|
|
- images
|
|
- voiceover audio
|
|
- optional video clips
|
|
- asset log
|
|
|
|
Image and audio generation can be automated later. Image-to-video remains manual for now.
|
|
|
|
### Stage 6: Editing
|
|
|
|
Editing remains manual initially.
|
|
|
|
Video Workbench should provide edit notes and timeline plan, not assume full editing automation.
|
|
|
|
### Stage 7: Publishing
|
|
|
|
Publishing remains manual initially.
|
|
|
|
Video Workbench can prepare platform copy:
|
|
|
|
- title options
|
|
- description
|
|
- cover copy
|
|
- hashtags / tags
|
|
- final script
|
|
|
|
## Project Shape
|
|
|
|
Use `series/` for multi-episode work and `standalone/` for one-off videos.
|
|
|
|
Each episode should preserve both process and final outputs. The canonical expanded episode structure is in:
|
|
|
|
```text
|
|
templates/episode-project/EPISODE_STRUCTURE.md
|
|
```
|
|
|
|
## Two Modes
|
|
|
|
### Execution Mode
|
|
|
|
Use existing sources, files, CCPE assets, and automation skills to complete work for the current video package.
|
|
|
|
Execution mode may prepare source maps, angle proposals, selected angle records, outlines, storyboards, shot-level production files, voiceover scripts, image prompts, asset logs, editing checklists, publishing copy, status records, and user decision records.
|
|
|
|
Execution mode must not invent missing formal agent output or treat planned capabilities as executed.
|
|
|
|
### Capability-Request Mode
|
|
|
|
When an agent, skill, runtime, model card, invocation protocol, or deterministic automation tool is missing, create a supplier ticket and pause the dependent part of the work.
|
|
|
|
Tickets go to:
|
|
|
|
```text
|
|
requirements/ccpe/
|
|
requirements/skills-vault/
|
|
```
|
|
|
|
CCPE supplies local work agents, runtime rules, model cards, invocation contracts, governed cognitive assets, and external capability registrations.
|
|
|
|
Skills-vault supplies deterministic automation tools, scripts, batch utilities, exporters, and installable automation skills.
|
|
|
|
## New Session Instruction
|
|
|
|
Use this in a new Video Workbench session:
|
|
|
|
```md
|
|
Please read README.md, VIDEO_WORKBENCH.md, docs/context-handoff.md, and docs/ccpe-system-handoff.md first, then continue work on Video Workbench according to those conventions.
|
|
```
|