Video Workbench

Video Workbench is the production workspace for dimensional output: turning deep essays, models, and ideas into short public-facing video packages.

It is a sibling of Writing Workbench, not a subfolder of it.

Position

Knowledge Vault      = source archive, formal essays, human model documents, historical discussions
Writing Workbench    = deep article production workspace
Video Workbench      = dimensional video output production workspace
CCPE System          = AI cognitive asset engineering workspace
Delivery Systems     = deployable external agentic products

See PROJECTS.md for the local project relationship map and ownership boundaries.

Mission

This workspace manages the process of extracting one or two accessible points from deep essays or models and producing a video-ready package, usually under 10 minutes.

It preserves:

• series architecture
• episode scope
• angle proposals
• selected angle
• video outline
• global visual style
• storyboard logic
• shot-level deep production
• voiceover script
• image prompts
• generated image/audio assets
• editing notes
• publishing copy

Boundaries

• Deep essays and human model documents remain in knowledge-vault.
• Deep article creation remains in writing-workbench.
• Actors, Skills, Model Cards, and Runtimes are maintained in ccpe-system.
• Deterministic reusable automation tools are maintained in skills-vault.
• Video Workbench records production work and capability requests; it does not store canonical prompts or agent definitions.
• Manual editing and publishing remain human-controlled unless explicitly automated later.

Two Modes

Execution Mode

Use existing sources, agents, skills, files, and project records to complete work for a video package.

Execution mode may:

• prepare source maps and source digests;
• create series or standalone project records when requested;
• prepare angle proposals, outlines, storyboards, shot files, scripts, prompts, asset logs, editing notes, and publishing copy;
• call existing CCPE assets or automation skills when they are available and appropriate;
• record user decisions and project status.

Execution mode must not invent missing formal agent output or treat a planned capability as already executed.

Capability-Request Mode

When an agent, skill, runtime, model card, invocation protocol, or deterministic automation tool is missing, create a supplier ticket and pause that capability-dependent part of the project.

Tickets go to:

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.

Starting A New Session

In a new Codex session opened on this project, use:

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.