docs: update video workbench operating boundaries

PROJECTS.md

@@ -0,0 +1,57 @@
+# 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 deep source material into public-facing video 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 | CCPE-Lite actors, agent specs, runtime rules, invocation contracts, model usage rules | 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`.
+- 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-projects` repository, 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:
+
+```text
+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.
+skills-vault provides deterministic automation tools.
+video-workbench runs the video project and keeps the production record.
+```
+

README.md

@@ -14,6 +14,8 @@ 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.
@@ -39,8 +41,41 @@ It preserves:
 - 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:
+
+```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.
+
 ## Starting A New Session
 
 In a new Codex session opened on this project, use:
@@ -48,4 +83,3 @@ In a new Codex session opened on this project, use:
 ```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.
 ```
-

VIDEO_WORKBENCH.md

@@ -21,6 +21,7 @@ knowledge-vault/sayings
 knowledge-vault/rules
 knowledge-vault/sources
 knowledge-vault/discussions
+writing-workbench/projects
 ```
 
 Common inputs:
@@ -32,6 +33,8 @@ Common inputs:
 - a target audience/topic
 - optional series plan
 
+Video Workbench is normally downstream of already formed source material. It may start from different upstream entrances when the user asks, but it should not quietly turn open-ended deep creation into a video production project.
+
 ## 4. Production Types
 
 Use `series/` when a long essay or model needs multiple episodes.
@@ -82,7 +85,32 @@ Video generation from images remains manual or semi-manual for now because outpu
 
 Editing and publishing are human-controlled in the initial version.
 
-## 8. CCPE Consumption
+## 8. Two Modes
+
+### Execution Mode
+
+Use existing project files, source materials, CCPE assets, and automation skills to produce or update a concrete video package.
+
+Execution mode may create and update project records, production files, user decision records, source maps, outlines, storyboards, scripts, prompts, asset logs, editing checklists, and publishing copy.
+
+Execution mode must not role-play a missing expert agent, mark planned skills as executed, or promote exploratory notes into formal outputs without user direction.
+
+### Capability-Request Mode
+
+When a required capability is missing, create a supplier ticket and pause the dependent work.
+
+Tickets go to:
+
+```text
+requirements/ccpe/
+requirements/skills-vault/
+```
+
+Use `requirements/ccpe/` for local work agents, CCPE-Lite artifacts, agent specs, runtime rules, model cards, invocation contracts, and governed cognitive assets.
+
+Use `requirements/skills-vault/` for deterministic automation tools, scripts, exporters, batch processors, and installable automation skills.
+
+## 9. CCPE Consumption
 
 Video Workbench consumes CCPE assets from:
 
@@ -103,5 +131,6 @@ Likely assets:
 - visual style model card
 - short video production runtime
 
-Do not duplicate canonical CCPE definitions here. Use `ccpe-consumption/` for links and usage notes.
+Do not duplicate canonical CCPE definitions here. Use `ccpe-consumption/` for links, usage notes, planned dependencies, and task-specific adapters.
 
+Local work prompts and agents belong in CCPE. If this workflow is later packaged as deployable software, production/business agent implementation belongs in the target software project, not in Video Workbench.

ccpe-consumption/runtime-links.md

@@ -27,3 +27,16 @@ C:\Users\wangq\Documents\Codex\ccpe-system
 
 Do not copy canonical CCPE artifacts here. Record links, usage notes, and task-specific adapters only.
 
+Video Workbench does not store canonical prompts, agent specs, model cards, or runtime specs. Missing CCPE capabilities should be requested through:
+
+```text
+requirements/ccpe/
+```
+
+Deterministic automation tools should be requested through:
+
+```text
+requirements/skills-vault/
+```
+
+Do not mark planned assets as executed or available until they have a real source path and validation record.

docs/ccpe-system-handoff.md

@@ -34,17 +34,20 @@ Purpose:
 Transform deep essays and models into public-facing short video plans, scripts, visual prompts, and production packages.
 ```
 
+This actor should remain a CCPE-owned local work asset. Video Workbench may request, consume, and validate it, but should not store its canonical prompt or agent definition.
+
 ## Recommended CCPE Build Sequence
 
 1. Upgrade `强哥的徒弟` into a verified CCPE-Lite artifact.
-2. Preserve regression tests against the original workflow:
+2. Validate it through a real Video Workbench project when the user starts one.
+3. Preserve regression tests against the original workflow:
    - angle proposals
    - video outline
    - storyboard logic
    - shot deep production
-3. Run Scenario Probe before promoting to Agent Spec or Skill.
+4. Run Scenario Probe before promoting to Agent Spec or Skill.
-4. Extract stable embedded models into Model Cards only when they are reusable beyond this actor.
+5. Extract stable embedded models into Model Cards only when they are reusable beyond this actor.
-5. Build small Skills only for repeatable actions:
+6. Build small Skills only for repeatable actions:
    - source-to-episode splitter
    - angle proposal generator
    - global visual style builder
@@ -53,8 +56,8 @@ Transform deep essays and models into public-facing short video plans, scripts,
    - image prompt generator
    - voiceover script generator
    - publish copy generator
-6. Build a `Short Video Production Runtime` only after the core stages are stable.
+7. Build a `Short Video Production Runtime` only after the core stages are stable.
-7. Validate the runtime with a trial Video Workbench project.
+8. Validate the runtime with a trial Video Workbench project.
 
 ## Candidate Asset Map
 
@@ -100,6 +103,12 @@ They share sources and sometimes models, but they differ in:
 - asset generation
 - evaluation criteria
 
+## Relationship To Deployable Systems
+
+CCPE can design local work agents and can also specify production/business agents for deployable systems. For deployable systems, CCPE owns specifications, boundaries, authority, evaluation, and invocation contracts.
+
+Implementation that depends on LangGraph, CrewAI, server deployment, persistence, monitoring, or product runtime constraints belongs in the target software project, such as a future `work-projects` repository. Video Workbench remains the local workflow and production-record workspace.
+
 ## Validation Target
 
 The first validation project should use one existing deep essay and one existing model document from Knowledge Vault.
@@ -113,4 +122,3 @@ Expected success:
 - a complete storyboard
 - shot-level prompts and voiceover
 - a package ready for manual editing
-

docs/context-handoff.md

@@ -13,6 +13,8 @@ CCPE System          = actor, skill, model, and runtime factory
 
 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 video production records. It does not own canonical prompts, agent definitions, reusable automation source code, or production/business agent implementation for deployable systems.
+
 ## User's Dimensional Output Workflow
 
 The user's deep essays are often 7,000 to 50,000 Chinese characters. Direct decompression into public form can multiply the text volume, which does not fit current public reading habits.
@@ -132,6 +134,31 @@ Each episode should preserve both process and final outputs. The canonical expan
 templates/episode-project/EPISODE_STRUCTURE.md
 ```
 
+## Two Modes
+
+### Execution Mode
+
+Use existing sources, files, CCPE assets, and automation skills to complete work for the current video package.
+
+Execution mode may prepare source maps, angle proposals, selected angle records, outlines, storyboards, shot-level production files, voiceover scripts, image prompts, asset logs, editing checklists, publishing copy, status records, and user decision records.
+
+Execution mode must not invent missing formal agent output or treat planned capabilities as 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 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:
@@ -139,4 +166,3 @@ 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.
 ```
-

requirements/ccpe/README.md

@@ -0,0 +1,12 @@
+# CCPE Capability Requests
+
+This directory holds supplier tickets for capabilities that should be designed or maintained in:
+
+```text
+C:\Users\wangq\Documents\Codex\ccpe-system
+```
+
+Use this directory when Video Workbench needs a local work agent, CCPE-Lite prompt card, agent spec, runtime rule, model card, invocation protocol, evaluation rule, or external capability registration.
+
+Do not place canonical prompts, agent specs, model cards, or runtime specs in this repository. This directory records the request from Video Workbench as the client project.
+

requirements/skills-vault/README.md

@@ -0,0 +1,12 @@
+# Skills-Vault Capability Requests
+
+This directory holds supplier tickets for capabilities that should be implemented or maintained in:
+
+```text
+C:\Users\wangq\Documents\Codex\skills-vault
+```
+
+Use this directory when Video Workbench needs a deterministic automation tool, script, batch processor, export helper, asset utility, or installable automation skill.
+
+Do not place reusable automation source code in this repository. This directory records the request from Video Workbench as the client project.
+