3.4 KiB
3.4 KiB
Project Relationships
This file is the local project map for Video Workbench. It exists so future sessions understand what this repository consumes, what it produces, and which neighboring repository owns each kind of asset.
Local Identity
video-workbench is the local production workspace for dimensional video output.
It turns accepted planning material and deep source references into public-facing video or slide-style execution packages, including:
- series architecture;
- episode scope;
- angle proposals;
- selected angle records;
- video outlines;
- storyboard logic;
- shot-level production files;
- voiceover scripts;
- image prompts;
- asset manifests;
- editing checklists;
- publishing copy.
It does not own upstream deep creation, canonical agents, reusable automation source code, or deployed production agent implementations.
Neighboring Projects
| Project | Relationship To Video Workbench | Video Workbench Consumes | Video Workbench Produces |
|---|---|---|---|
knowledge-vault |
Upstream knowledge, source archive, formal essays, human-readable model documents, and discussion memory | stable essays, model documents, selected source notes, source paths, discussion records with formed conclusions | optional pointers from video packages back to source materials |
writing-workbench |
Sibling workspace for deep article production | completed or sufficiently stable article projects when the user chooses to make video content | no default output |
ccpe-system |
Supplier of local work agents, runtime rules, model cards, and governed cognitive assets | the external Interface.md, the consumer setup contract, and task-specific canonical artifacts only when routed by the setup/registry |
capability requests under requirements/ccpe/ |
skills-vault |
Supplier of deterministic automation tools | file processors, batch utilities, asset tools, export tools, installable automation skills | capability requests under requirements/skills-vault/ |
work-projects |
Separate software/customer project workspace | no default input | production system requirements if this video workflow is later packaged as deployable software |
Boundary Rules
- Video Workbench is a sibling of Writing Workbench, not a child project.
- Deep article creation belongs in
writing-workbench. - Long-term sources, finished essays, model documents, and open-ended discussion memory belong in
knowledge-vault. - Canonical local-work agents, prompts, runtimes, model cards, and invocation protocols belong in
ccpe-system; Video Workbench starts fromccpe-system\Interface.md, not from hardcoded internal CCPE artifact paths. - Deterministic reusable automation implementation source belongs in
skills-vault. - If the video workflow is later packaged as a deployable system, production/business agent implementation belongs in the relevant
work-projectsrepository, not in this local workbench. - Missing capabilities are requested through
requirements/, not implemented ad hoc inside this repository.
Practical Rule
Video Workbench is a client and production room:
knowledge-vault provides sources and long-term knowledge.
writing-workbench may provide stable article projects.
ccpe-system provides local work agents, protocols, and model assets through `Interface.md`.
skills-vault provides deterministic automation tools.
video-workbench runs local projects under `projects/` and keeps lightweight execution records.