diff --git a/README.md b/README.md index 610e076..cf3fb3f 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,15 @@ # 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. +Video Workbench is the local execution workspace for dimensional video and slide-style output. It receives GPT V2 planning Markdown from the user, keeps lightweight project records, and produces local execution plans, visual-system assets, 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 +GPT / ChatGPT = stage 0-5 planning Markdown, outlines, visual systems, page/shot skeletons User = decisions, source material, accepted planning files -Video Workbench = project notes, execution, generated assets, handoff +Video Workbench = stage 6+ execution planning, Prompt Advisor work, visual-system materialization, generated assets, handoff CCPE System = local work agents, runtimes, model cards, interfaces Skills Vault = reusable automation skills and deterministic tools ``` @@ -23,24 +23,31 @@ projects/ project-id/ project.md intake/ + execution-plan.md + visual-system/ + visual-system.md + refs/ + iterations/ slides/ slides.md s01/ s02/ handoff/ -tmp/ +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//intake/` holds user-provided GPT planning output, source notes, execution packages, references, and other accepted inputs. +- `projects//intake/` holds user-provided GPT V2 stage 0-5 Markdown, source notes, references, and other accepted inputs. - `projects//project.md` is a Codex-maintained project note and file map. It should link to content in `intake/`, not duplicate it. -- `projects//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. +- `projects//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//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//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. -- `tmp/` is for local temporary files. +- `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. @@ -49,6 +56,9 @@ Series indexes can be added later under `projects/_series/` when a real series n - 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. +- Codex does not ask GPT V2 for final image prompts, Codex JSON, output paths, task lists, or image generation parameters. +- `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`. diff --git a/VIDEO_WORKBENCH.md b/VIDEO_WORKBENCH.md index 3bf2501..8473be9 100644 --- a/VIDEO_WORKBENCH.md +++ b/VIDEO_WORKBENCH.md @@ -4,17 +4,19 @@ 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. +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 = plans, outlines, storyboards, execution packages +GPT / ChatGPT = stage 0-5 planning Markdown, outlines, visual systems, page/shot skeletons User = decisions, accepted inputs, source/reference material -Codex = project notes, file mapping, execution, local assets +Codex = stage 6+ execution planning, Prompt Advisor work, visual-system materialization, iteration, local assets ``` -Codex should not rewrite GPT planning into duplicate project content. The accepted planning files belong in the project `intake/` directory. +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 @@ -25,6 +27,11 @@ projects/ project-id/ project.md intake/ + execution-plan.md + visual-system/ + visual-system.md + refs/ + iterations/ slides/ slides.md s01/ @@ -44,31 +51,82 @@ If a series needs more structure, create `projects/_series/` when the first real - project status; - medium type; - source and reference links; -- which `intake/` files are the outline, storyboard, execution package, or background notes; +- 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, shot design, or execution package. +It should not duplicate the full outline, storyboard, page design, shot design, or execution plan. -## 5. Intake +## 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 planning documents; +- GPT V2 stage 0-5 planning Markdown; - outlines; -- storyboards; -- detailed slide or shot designs; -- execution packages; +- 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. -## 6. Slides And Shots +## 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 lightweight mapping and progress tracker, similar to Writing Workbench's `drafting/drafting.md`. +`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: @@ -76,16 +134,28 @@ Each `slides/sNN/` folder keeps one slide, page, or shot together: slides/ slides.md s01/ - prompt files - voiceover files - generated images - generated audio - local notes + 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 ``` -Exact file names inside `sNN/` should be chosen when that unit is executed. +All files inside `sNN/` must carry the `sNN` prefix. Iteration files use `sNN-vN-type.ext`, so files from the same version sort together. -## 7. Word Budget +## 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: @@ -96,7 +166,7 @@ Use the default standard: Adjust only when the user specifies a different narration speed. -## 8. Asset Policy +## 11. Asset Policy Image and audio generation can be automated when available skills or APIs are appropriate. @@ -104,7 +174,9 @@ Video generation from images remains manual or semi-manual for now because outpu Editing and publishing are human-controlled unless explicitly automated later. -## 9. Capability-Request Mode +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. @@ -119,7 +191,7 @@ Use `requirements/ccpe/` for local work agents, CCPE-Lite artifacts, agent specs Use `requirements/skills-vault/` for deterministic automation tools, scripts, exporters, batch processors, and installable automation skills. -## 10. Text Encoding +## 13. Text Encoding All local project documents are UTF-8 unless a file explicitly declares another encoding. @@ -132,7 +204,7 @@ Select-String -Path -Pattern -Encoding UTF8 Do not wait for mojibake or a failed first read before applying UTF-8. -## 11. CCPE Consumption +## 14. CCPE Consumption Video Workbench consumes CCPE through the single external interface: diff --git a/docs/context-handoff.md b/docs/context-handoff.md index b791638..97237e3 100644 --- a/docs/context-handoff.md +++ b/docs/context-handoff.md @@ -19,12 +19,14 @@ Video Workbench keeps local project notes, execution outputs, and handoff record ## Collaboration Contract ```text -GPT / ChatGPT = planning and execution-package authoring +GPT / ChatGPT = stage 0-5 planning Markdown, visual-system design, page/shot skeletons User = decisions and accepted input placement -Codex = file mapping, project notes, execution, generated assets +Codex = stage 6+ execution planning, Prompt Advisor work, visual-system materialization, iteration, generated assets ``` -Most content files should come from GPT output accepted by the user and placed in `projects//intake/`. Codex-maintained files should be short continuation aids and execution records. +Most planning files should come from GPT V2 output accepted by the user and placed in `projects//intake/`. Codex-maintained files should be local execution aids and execution records. + +Codex should not ask GPT V2 for final image prompts, Codex JSON, output paths, task lists, or image generation parameters. GPT V2 planning Markdown is a source specification, not an execution command. ## Project Shape @@ -44,6 +46,11 @@ Recommended project-local structure: projects// project.md intake/ + execution-plan.md + visual-system/ + visual-system.md + refs/ + iterations/ slides/ slides.md s01/ @@ -54,13 +61,25 @@ Use root `handoff/` for repo-level, cross-project, series-level, or context-wind ## Project Files -`project.md` is a Codex-maintained small note. It should link to intake files instead of duplicating the outline, storyboard, or execution package. +`project.md` is a Codex-maintained small note. It should link to intake files and key local execution files instead of duplicating the outline, storyboard, page design, or execution plan. -`intake/` holds GPT planning material, user-provided source material, references, execution packages, and other accepted input files. +`intake/` holds GPT V2 stage 0-5 planning Markdown, user-provided source material, references, and other accepted input files. -`slides/slides.md` is the slide/page/shot mapping and progress tracker. It is the Video Workbench equivalent of a lightweight drafting tracker. +`execution-plan.md` is the visual project's local execution control file. It records the current medium branch, visual-system materialization targets, small-batch iteration strategy, active `sNN` units, current round, and next decision. It does not repeat the project map from `project.md`. -`slides/sNN/` keeps all files for one slide, page, or shot together: prompts, narration, generated images, generated audio, and local notes. +`visual-system/visual-system.md` records the current accepted visual system, materialization targets, iteration log, failure attribution, and next action. Character anchors, scene anchors, templates, diagrams, and backgrounds belong under `visual-system/`, not a separate `makeup-still/`. + +`slides/slides.md` is the slide/page/shot execution fact table. It records each unit's source, batch, prompt version, image version, review state, acceptance state, and notes. It does not replace `execution-plan.md`. + +`slides/sNN/` keeps all files for one slide, page, or shot together: prompts, narration, generated images, generated audio, review notes, and local notes. Every file inside `sNN/` must carry the `sNN` prefix; iteration files use `sNN-vN-type.ext`, such as `s03-v1-prompt.md`. + +## Investigations + +Use `investigations/` for research reports, experiments, comparisons, draft workflow proposals, and reviewable evidence. + +`tmp/` is deprecated. New durable investigation material should go under `investigations/`; short-lived scratch material should be deleted when no longer needed. + +`garden-gpt-image-2/` remains reserved for tool-level image prompt or workflow traces when that path is used. ## Text Encoding