100 lines
3.7 KiB
Markdown
100 lines
3.7 KiB
Markdown
# 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 = planning and execution-package authoring
|
|
User = decisions and accepted input placement
|
|
Codex = file mapping, project notes, execution, generated assets
|
|
```
|
|
|
|
Most content files should come from GPT output accepted by the user and placed in `projects/<project>/intake/`. Codex-maintained files should be short continuation aids and execution records.
|
|
|
|
## Project Shape
|
|
|
|
Use one project root:
|
|
|
|
```text
|
|
projects/<project-id>/
|
|
```
|
|
|
|
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-id>/
|
|
project.md
|
|
intake/
|
|
slides/
|
|
slides.md
|
|
s01/
|
|
s02/
|
|
```
|
|
|
|
Use root `handoff/` for repo-level, cross-project, series-level, or context-window handoff notes.
|
|
|
|
## 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.
|
|
|
|
`intake/` holds GPT planning material, user-provided source material, references, execution packages, 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.
|
|
|
|
`slides/sNN/` keeps all files for one slide, page, or shot together: prompts, narration, generated images, generated audio, and local notes.
|
|
|
|
## 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.
|
|
|
|
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 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.
|
|
```
|