video-workbench/README.md

62 lines
2.6 KiB
Markdown

# Video Workbench
Video Workbench is the local execution workspace for dimensional video and slide-style output. It receives GPT planning material from the user, keeps lightweight project records, and produces local assets such as prompts, images, narration audio, slide/page files, and handoff notes.
It is a sibling of Writing Workbench, not a subfolder of it.
## Working Model
```text
GPT / ChatGPT = planning, outlines, storyboards, execution packages
User = decisions, source material, accepted planning files
Video Workbench = project notes, execution, generated assets, handoff
CCPE System = local work agents, runtimes, model cards, interfaces
Skills Vault = reusable automation skills and deterministic tools
```
Video Workbench is not the canonical home for prompts, agents, reusable automation source, deep essays, or finished article writing.
## Main Layout
```text
projects/
project-id/
project.md
intake/
slides/
slides.md
s01/
s02/
handoff/
tmp/
garden-gpt-image-2/
requirements/
ccpe-consumption/
```
- `projects/` is the only project entry point. Project status and series membership are recorded inside project files, not by moving directories.
- `projects/<project>/intake/` holds user-provided GPT planning output, source notes, execution packages, references, and other accepted inputs.
- `projects/<project>/project.md` is a Codex-maintained project note and file map. It should link to content in `intake/`, not duplicate it.
- `projects/<project>/slides/` is the working area for slide, page, or shot execution. Each `sNN/` folder keeps that unit's prompts, narration, generated images, audio, and local notes together.
- `handoff/` is for repo-level, cross-project, or context-window handoff notes.
- `tmp/` is for local temporary files.
- `garden-gpt-image-2/` is reserved for local image-generation prompt/workflow traces when that tool path is used.
Series indexes can be added later under `projects/_series/` when a real series needs more than project-local notes.
## Boundaries
- Manual editing and publishing remain human-controlled unless explicitly automated later.
- Video Workbench does not default to full video editing, image-to-video generation, or platform publishing.
- Missing CCPE assets should be requested under `requirements/ccpe/`.
- Missing reusable automation should be requested under `requirements/skills-vault/`.
## Starting A New Session
In a new Codex session opened on this project, use:
```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.
```