# Video Workbench Context Handoff This document preserves the current working agreements for Video Workbench so future Codex sessions do not depend on copied chat history. ## Confirmed Architecture ```text Knowledge Vault = source archive and model/essay library Writing Workbench = deep article production workspace Video Workbench = local video/slide execution workspace CCPE System = actor, skill, model, runtime, and interface supplier Skills Vault = reusable automation skill supplier ``` Video Workbench is a sibling of Writing Workbench. It should not be folded into article production because the target output, rhythm, assets, and evaluation criteria are different. Video Workbench keeps local project notes, execution outputs, and handoff records. It does not own canonical prompts, agent definitions, reusable automation source code, or production/business agent implementation for deployable systems. ## Collaboration Contract ```text GPT / ChatGPT = stage 0-5 planning Markdown, visual-system design, page/shot skeletons User = decisions and accepted input placement Codex = stage 6+ execution planning, Prompt Advisor work, visual-system materialization, iteration, generated assets ``` 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 Use one project root: ```text projects// ``` Do not move projects between status folders. Record status in `project.md`. Do not decide series vs standalone through directory placement. Record series membership in `project.md`; add `projects/_series/` only when a real series needs shared files or an index. Recommended project-local structure: ```text projects// project.md intake/ execution-plan.md visual-system/ visual-system.md refs/ iterations/ slides/ slides.md s01/ s02/ ``` Use root `handoff/` for repo-level, cross-project, series-level, or context-window handoff notes. Use `docs/cases/` as the local Codex case-pattern library. It is allowed to extract structure, page or shot granularity, speaker-note style, visual asset layering, and review dimensions from old GPT cases, but it must not re-import old final-prompt, Codex JSON, output-path, or global text-rendering rules. ## Project Files `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 V2 stage 0-5 planning Markdown, user-provided source material, references, and other accepted input files. `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`. `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 All local Markdown, JSON, YAML, text, prompt, discussion, and handoff files are UTF-8 unless a file explicitly declares another encoding. Use explicit UTF-8 when reading these files from PowerShell: ```powershell Get-Content -LiteralPath -Encoding UTF8 Select-String -Path -Pattern -Encoding UTF8 ``` ## Dimensional Output Rule The user's method: ```text Extract one or two points from a deep article or model. Connect them to a public-facing concern. Produce a video usually under 10 minutes. Use about 220 Chinese characters per minute as the narration budget. ``` Editing and publishing remain manual unless explicitly automated later. Image-to-video remains manual or semi-manual for now. ## Capability-Request Mode When an agent, skill, runtime, model card, invocation protocol, or deterministic automation tool is missing, create a supplier ticket and pause the dependent part of the work. Tickets go to: ```text requirements/ccpe/ requirements/skills-vault/ ``` CCPE supplies local work agents, runtime rules, model cards, invocation contracts, governed cognitive assets, and external capability registrations. The single CCPE external interface is: ```text C:\Users\wangq\Documents\Codex\ccpe-system\Interface.md ``` Read that file first, then follow it to the consumer setup contract. Do not use older Agent, Lite, Skill, Runtime, or protocol paths as default startup paths. Skills-vault supplies deterministic automation tools, scripts, batch utilities, exporters, and installable automation skills. ## New Session Instruction Use this in a new Video Workbench session: ```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. ```