# VIDEO_WORKBENCH.md ## 1. Workspace Identity This project is the local execution workspace for dimensional video and slide-style output. It turns accepted GPT V2 planning Markdown and user-provided sources into project notes, local execution plans, visual-system assets, slide/page execution folders, generated assets, and handoff material. It is optimized for practical continuation, not heavy governance. ## 2. Collaboration Roles ```text GPT / ChatGPT = stage 0-5 planning Markdown, outlines, visual systems, page/shot skeletons User = decisions, accepted inputs, source/reference material Codex = stage 6+ execution planning, Prompt Advisor work, visual-system materialization, iteration, local assets ``` GPT V2 does not provide final image prompts, Codex JSON, output paths, task lists, or image generation parameters. Codex should not request those from GPT as missing inputs. Codex should not rewrite GPT planning into duplicate project content. The accepted planning files belong in the project `intake/` directory, and Codex turns them into local execution decisions in `execution-plan.md`. ## 3. Project Layout All video or slide-style work lives under `projects/`: ```text projects/ project-id/ project.md intake/ execution-plan.md visual-system/ visual-system.md refs/ iterations/ 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.md` is a lightweight Codex-maintained note. It should record: - project status; - medium type; - source and reference links; - which `intake/` files are GPT V2 planning Markdown, source notes, reference notes, or background notes; - current execution focus; - key local execution files; - next action. It should not duplicate the full outline, storyboard, page design, shot design, or execution plan. ## 5. Execution Plan Visual projects must have: ```text projects//execution-plan.md ``` This is a living Codex-maintained execution control file. It records: - the current medium branch; - the current execution focus; - which visual-system assets need materialization; - the current small-batch iteration strategy; - which `sNN` units are in the active batch; - the current round; - the next decision. It should not repeat the project ID, full intake file index, or project map from `project.md`. ## 6. Intake `projects//intake/` holds material provided or accepted by the user: - GPT V2 stage 0-5 planning Markdown; - outlines; - storyboards, page skeletons, or shot skeletons; - 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. ## 7. Visual System Visual projects use: ```text projects//visual-system/ visual-system.md refs/ iterations/ ``` `visual-system.md` is the single record for the project's public visual system. It should cover: - the current accepted visual system; - materialization targets; - trial prompts and generated reference assets; - review notes; - failure attribution; - next action. Use optional subfolders only when the project needs them: ```text visual-system/characters/ visual-system/scenes/ visual-system/templates/ visual-system/diagrams/ visual-system/backgrounds/ ``` Do not create a separate `makeup-still/` directory. Character anchors and identity references belong under `visual-system/`. ## 8. Slides And Shots Use `slides/` as the execution unit area for both video shots and PPT-style pages. `projects//slides/slides.md` is the unit execution fact table. It records each page or shot's source, batch, current prompt version, current image version, review state, acceptance state, and notes. Project-level iteration strategy belongs in `execution-plan.md`. Each `slides/sNN/` folder keeps one slide, page, or shot together: ```text slides/ slides.md s01/ s01-metadata.json s01-unit-spec.md s01-visual-brief.md s01-v1-prompt.md s01-v1-image.png s01-v1-review.md s01-v2-prompt.md s01-v2-image.png s01-v2-review.md ``` All files inside `sNN/` must carry the `sNN` prefix. Iteration files use `sNN-vN-type.ext`, so files from the same version sort together. ## 9. Investigations Use `investigations/` for research reports, experiments, comparisons, draft workflow proposals, and other reviewable evidence. `tmp/` is deprecated and should not receive new durable work. Short-lived scratch material should either be deleted or promoted into `investigations/` when it becomes useful evidence. `garden-gpt-image-2/` remains reserved for tool-level image prompt or workflow traces when that path is used. ## 10. 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. ## 11. 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. Codex is the default prompt owner for final image prompts in this workspace. It may use `gpt-image-2` Advisor or other image tools, but GPT V2 planning Markdown remains a source specification, not a final prompt. ## 12. 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. ## 13. Text Encoding All local project documents are UTF-8 unless a file explicitly declares another encoding. When using PowerShell to read Markdown, JSON, YAML, text, handoff, prompt, or discussion files, use explicit UTF-8: ```powershell Get-Content -LiteralPath -Encoding UTF8 Select-String -Path -Pattern -Encoding UTF8 ``` Do not wait for mojibake or a failed first read before applying UTF-8. ## 14. CCPE Consumption Video Workbench consumes CCPE through the single external interface: ```text C:\Users\wangq\Documents\Codex\ccpe-system\Interface.md ``` When preparing CCPE integration or invocation work, read `Interface.md` first and follow it to: ```text C:\Users\wangq\Documents\Codex\ccpe-system\runtimes\hybrid\ccpe-agent-consumer-setup.md ``` Do not duplicate canonical CCPE definitions here. Do not hardcode Agent, Lite, Skill, Runtime, or protocol paths as default entrypoints. Use `ccpe-consumption/` for interface notes and future project-local invocation setup 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.