133 lines
4.1 KiB
Markdown
133 lines
4.1 KiB
Markdown
# VIDEO_WORKBENCH.md
|
|
|
|
## 1. Workspace Identity
|
|
|
|
This project is the local execution workspace for dimensional video and slide-style output.
|
|
|
|
It turns accepted GPT planning material and user-provided sources into project notes, slide/page execution folders, generated assets, and handoff material. It is optimized for practical continuation, not heavy governance.
|
|
|
|
## 2. Collaboration Roles
|
|
|
|
```text
|
|
GPT / ChatGPT = plans, outlines, storyboards, execution packages
|
|
User = decisions, accepted inputs, source/reference material
|
|
Codex = project notes, file mapping, execution, local assets
|
|
```
|
|
|
|
Codex should not rewrite GPT planning into duplicate project content. The accepted planning files belong in the project `intake/` directory.
|
|
|
|
## 3. Project Layout
|
|
|
|
All video or slide-style work lives under `projects/`:
|
|
|
|
```text
|
|
projects/
|
|
project-id/
|
|
project.md
|
|
intake/
|
|
slides/
|
|
slides.md
|
|
s01/
|
|
s02/
|
|
```
|
|
|
|
Use root-level `handoff/` for repository-level, cross-project, series-level, or context-window handoff notes.
|
|
|
|
Do not split projects into `active`, `completed`, `abandoned`, `series`, or `standalone` folders. Status and series membership belong in project files because both can change during real production.
|
|
|
|
If a series needs more structure, create `projects/_series/` when the first real series needs it.
|
|
|
|
## 4. Project Notes
|
|
|
|
`projects/<project>/project.md` is a lightweight Codex-maintained note. It should record:
|
|
|
|
- project status;
|
|
- medium type;
|
|
- source and reference links;
|
|
- which `intake/` files are the outline, storyboard, execution package, or background notes;
|
|
- current execution focus;
|
|
- next action.
|
|
|
|
It should not duplicate the full outline, storyboard, shot design, or execution package.
|
|
|
|
## 5. Intake
|
|
|
|
`projects/<project>/intake/` holds material provided or accepted by the user:
|
|
|
|
- GPT planning documents;
|
|
- outlines;
|
|
- storyboards;
|
|
- detailed slide or shot designs;
|
|
- execution packages;
|
|
- background notes;
|
|
- reference images, audio notes, or source pointers.
|
|
|
|
File naming can be agreed during the first real project. Do not create a rigid naming scheme before the real GPT outputs are known.
|
|
|
|
## 6. Slides And Shots
|
|
|
|
Use `slides/` as the execution unit area for both video shots and PPT-style pages.
|
|
|
|
`projects/<project>/slides/slides.md` is the lightweight mapping and progress tracker, similar to Writing Workbench's `drafting/drafting.md`.
|
|
|
|
Each `slides/sNN/` folder keeps one slide, page, or shot together:
|
|
|
|
```text
|
|
slides/
|
|
slides.md
|
|
s01/
|
|
prompt files
|
|
voiceover files
|
|
generated images
|
|
generated audio
|
|
local notes
|
|
```
|
|
|
|
Exact file names inside `sNN/` should be chosen when that unit is executed.
|
|
|
|
## 7. 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.
|
|
|
|
## 8. Asset Policy
|
|
|
|
Image and audio generation can be automated when available skills or APIs are appropriate.
|
|
|
|
Video generation from images remains manual or semi-manual for now because output reliability varies.
|
|
|
|
Editing and publishing are human-controlled unless explicitly automated later.
|
|
|
|
## 9. 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.
|
|
|
|
## 10. CCPE Consumption
|
|
|
|
Video Workbench consumes CCPE assets from:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\ccpe-system
|
|
```
|
|
|
|
Do not duplicate canonical CCPE definitions here. Use `ccpe-consumption/` for links, usage notes, planned dependencies, and future interface records.
|
|
|
|
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.
|