Go to file
wantsong 31b920e819 Add deck project text records 2026-07-07 17:11:01 +08:00
ccpe-consumption docs: align video workbench rules with CCPE interface 2026-06-22 13:45:46 +08:00
docs 记录媒体资产入库策略 2026-06-26 06:19:36 +08:00
garden-gpt-image-2 chore: simplify video workbench structure 2026-06-22 13:10:13 +08:00
handoff 完成在路上生产编排完成所有镜头制作 2026-06-25 10:22:34 +08:00
investigations 完成第五轮测试和回调调研 2026-06-24 20:58:05 +08:00
projects Add deck project text records 2026-07-07 17:11:01 +08:00
requirements Initialize On The Road video project 2026-06-23 13:25:58 +08:00
.gitignore Add deck project text records 2026-07-07 17:11:01 +08:00
AGENTS.md Add deck project text records 2026-07-07 17:11:01 +08:00
PROJECTS.md docs: align video workbench rules with CCPE interface 2026-06-22 13:45:46 +08:00
README.md docs: 完成 video workbench 重构案例库 2026-06-23 08:46:13 +08:00
VIDEO_WORKBENCH.md 完成在路上生产编排完成所有镜头制作 2026-06-25 10:22:34 +08:00

README.md

Video Workbench

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

GPT / ChatGPT      = stage 0-5 planning Markdown, outlines, visual systems, page/shot skeletons
User               = decisions, source material, accepted planning files
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

Video Workbench is not the canonical home for prompts, agents, reusable automation source, deep essays, or finished article writing.

Main Layout

projects/
  project-id/
    project.md
    intake/
    execution-plan.md
    visual-system/
      visual-system.md
      refs/
      iterations/
    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 V2 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>/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 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.
  • 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:

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.