video-workbench/README.md

84 lines
5.4 KiB
Markdown

# Video Workbench
Video Workbench is the local execution workspace for dimensional video, Remotion, and slide-style output. It receives GPT planning Markdown from the user, keeps lightweight project records, and produces local execution plans, visual-system assets, prompts, images, Remotion source projects, narration audio, renderable video files, slide/page files, and handoff notes.
It is a sibling of Writing Workbench, not a subfolder of it.
## Working Model
```text
GPT / ChatGPT = stage 0-5 planning Markdown, outlines, visual systems, page/shot skeletons, Remotion planning briefs
User = decisions, source material, accepted planning files
Video Workbench = stage 6+ execution planning, Prompt Advisor work, Remotion implementation, visual-system materialization, 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/
execution-plan.md
visual-system/
visual-system.md
refs/
iterations/
remotion/
package.json
src/
public/
slides/
slides.md
s01/
s02/
handoff/
docs/
cases/
investigations/
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 stage 0-5 Markdown, source notes, 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>/execution-plan.md` is the project-level execution control file for visual work. It records the current strategy, batch, round, and next decision instead of duplicating the project map.
- `projects/<project>/visual-system/visual-system.md` records the current accepted visual system, materialization targets, iteration log, failure attribution, and next action. Reference images and iteration artifacts stay under `refs/` and `iterations/`.
- `projects/<project>/remotion/` is the default source root for one-off project-specific Remotion videos. Keep source code, package files, and source assets there; keep generated renders, caches, and dependencies out of Git by default.
- `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. Files inside `sNN/` must carry the `sNN` prefix, and iteration files use `sNN-vN-type.ext`, such as `s03-v1-prompt.md`.
- `handoff/` is for repo-level, cross-project, or context-window handoff notes.
- `docs/cases/` is the Codex-side local case-pattern library extracted from old real GPT cases. It preserves execution patterns, not old prompts, JSON packages, paths, or global text-rendering rules.
- `investigations/` is for research reports, experiments, comparisons, and draft workflow proposals. It replaces `tmp/` for durable investigation evidence.
- `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 manual video editing, image-to-video generation, or platform publishing.
- Codex does not ask GPT for final image prompts, Codex JSON, output paths, task lists, dependency commands, render commands, or complete Remotion source code.
- For Remotion videos, accepted GPT planning can supply adaptation judgment, a style-system anchor, storyboard-to-component mapping, and a Remotion Implementation Brief. Codex owns the local source layout, implementation, dependency commands, render commands, and validation.
- The default Remotion deliverable is source code plus a renderable MP4. The user has standing task-level permission for `npx create-video`, npm dependency installation, and Remotion render commands when a Remotion task needs them; sandbox or network approvals may still be requested at command time.
- `makeup-still/` is not a recommended project directory. Character, scene, template, diagram, and background anchors belong under `visual-system/` when needed.
- `tmp/` is deprecated. New reusable or reviewable investigation material belongs under `investigations/`.
- Missing CCPE assets should be requested under `requirements/ccpe/`.
- Missing reusable automation should be requested under `requirements/skills-vault/`.
- All local Markdown, JSON, YAML, text, prompt, discussion, and handoff files are UTF-8 by default. PowerShell reads should use explicit `-Encoding UTF8`.
- The default CCPE external interface is `C:\Users\wangq\Documents\Codex\ccpe-system\Interface.md`; follow it to the consumer setup contract before reading narrower CCPE artifacts.
## Starting A New Session
In a new Codex session opened on this project, use:
```md
Please read AGENTS.md, 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.
```