137 lines
4.5 KiB
Markdown
137 lines
4.5 KiB
Markdown
# VIDEO_WORKBENCH.md
|
|
|
|
## 1. Workspace Identity
|
|
|
|
This project is the dimensional video output workspace.
|
|
|
|
It turns deep source material into public-facing short video production packages. It is optimized for accessibility, rhythm, metaphor, visual planning, and asset preparation.
|
|
|
|
## 2. Operating Principle
|
|
|
|
One video should usually explain one or two points.
|
|
|
|
The goal is not to compress a deep article into a shorter article. The goal is to extract a public-facing angle from a deep model or essay and rebuild it as a video-native experience.
|
|
|
|
## 3. Source Inputs
|
|
|
|
Typical sources:
|
|
|
|
```text
|
|
knowledge-vault/sayings
|
|
knowledge-vault/rules
|
|
knowledge-vault/sources
|
|
knowledge-vault/discussions
|
|
writing-workbench/projects
|
|
```
|
|
|
|
Common inputs:
|
|
|
|
- one long essay
|
|
- one human-facing model document
|
|
- selected source notes
|
|
- Deep Research reports
|
|
- a target audience/topic
|
|
- optional series plan
|
|
|
|
Video Workbench is normally downstream of already formed source material. It may start from different upstream entrances when the user asks, but it should not quietly turn open-ended deep creation into a video production project.
|
|
|
|
## 4. Production Types
|
|
|
|
Use `series/` when a long essay or model needs multiple episodes.
|
|
|
|
Use `standalone/` when the output is a single independent video.
|
|
|
|
Recommended project ids:
|
|
|
|
```text
|
|
series/active/YYYY-MM-DD-sNNN-temp-series/
|
|
standalone/active/YYYY-MM-DD-vNNN-temp-topic/
|
|
```
|
|
|
|
Do not rely on final titles in folder names. Titles can evolve inside `series.md`, `episode.md`, or publishing files.
|
|
|
|
## 5. Canonical Episode Stages
|
|
|
|
The workflow maps to the user's prior dimensional output process:
|
|
|
|
```text
|
|
00-architecture = series/episode architecture, source selection, word budget
|
|
01-proposals = three distinct angle proposals
|
|
02-tone-outline = selected angle, core anchor, metaphor, visual style, global prompt
|
|
03-storyboard = storyboard logic and time budget
|
|
04-deep-production = shot-level visual plan, image prompts, voiceover, design notes
|
|
05-assets = generated images, audio, optional video clips, asset log
|
|
06-editing = manual edit notes and timeline plan
|
|
07-publish = title options, description, platform copy, final script
|
|
08-review = review notes and postmortem
|
|
```
|
|
|
|
## 6. Word Budget
|
|
|
|
Use the default standard:
|
|
|
|
```text
|
|
1 minute = about 220 Chinese characters of voiceover
|
|
10 minutes = about 2200 Chinese characters
|
|
```
|
|
|
|
Adjust only when the user specifies a different narration speed.
|
|
|
|
## 7. Asset Policy
|
|
|
|
Image and audio generation can be automated when APIs and models are available.
|
|
|
|
Video generation from images remains manual or semi-manual for now because output reliability varies.
|
|
|
|
Editing and publishing are human-controlled in the initial version.
|
|
|
|
## 8. Two Modes
|
|
|
|
### Execution Mode
|
|
|
|
Use existing project files, source materials, CCPE assets, and automation skills to produce or update a concrete video package.
|
|
|
|
Execution mode may create and update project records, production files, user decision records, source maps, outlines, storyboards, scripts, prompts, asset logs, editing checklists, and publishing copy.
|
|
|
|
Execution mode must not role-play a missing expert agent, mark planned skills as executed, or promote exploratory notes into formal outputs without user direction.
|
|
|
|
### Capability-Request Mode
|
|
|
|
When a required capability is missing, create a supplier ticket and pause the dependent work.
|
|
|
|
Tickets go to:
|
|
|
|
```text
|
|
requirements/ccpe/
|
|
requirements/skills-vault/
|
|
```
|
|
|
|
Use `requirements/ccpe/` for local work agents, CCPE-Lite artifacts, agent specs, runtime rules, model cards, invocation contracts, and governed cognitive assets.
|
|
|
|
Use `requirements/skills-vault/` for deterministic automation tools, scripts, exporters, batch processors, and installable automation skills.
|
|
|
|
## 9. CCPE Consumption
|
|
|
|
Video Workbench consumes CCPE assets from:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\ccpe-system
|
|
```
|
|
|
|
Likely assets:
|
|
|
|
- Qiangge's Apprentice / dimensional output actor
|
|
- series architect
|
|
- angle proposal skill
|
|
- video outline skill
|
|
- storyboard skill
|
|
- shot deep-production skill
|
|
- image prompt generator
|
|
- voiceover script generator
|
|
- visual style model card
|
|
- short video production runtime
|
|
|
|
Do not duplicate canonical CCPE definitions here. Use `ccpe-consumption/` for links, usage notes, planned dependencies, and task-specific adapters.
|
|
|
|
Local work prompts and agents belong in CCPE. If this workflow is later packaged as deployable software, production/business agent implementation belongs in the target software project, not in Video Workbench.
|