chore: simplify video workbench structure
This commit is contained in:
parent
baafbd5711
commit
94043faba5
|
|
@ -0,0 +1,5 @@
|
|||
tmp/*
|
||||
!tmp/.gitkeep
|
||||
|
||||
garden-gpt-image-2/*
|
||||
!garden-gpt-image-2/.gitkeep
|
||||
|
|
@ -6,7 +6,7 @@ This file is the local project map for Video Workbench. It exists so future sess
|
|||
|
||||
`video-workbench` is the local production workspace for dimensional video output.
|
||||
|
||||
It turns deep source material into public-facing video packages, including:
|
||||
It turns accepted planning material and deep source references into public-facing video or slide-style execution packages, including:
|
||||
|
||||
- series architecture;
|
||||
- episode scope;
|
||||
|
|
@ -52,6 +52,5 @@ 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.
|
||||
video-workbench runs local projects under `projects/` and keeps lightweight execution records.
|
||||
```
|
||||
|
||||
|
|
|
|||
96
README.md
96
README.md
|
|
@ -1,80 +1,56 @@
|
|||
# Video Workbench
|
||||
|
||||
Video Workbench is the production workspace for dimensional output: turning deep essays, models, and ideas into short public-facing video packages.
|
||||
Video Workbench is the local execution workspace for dimensional video and slide-style output. It receives GPT planning material from the user, keeps lightweight project records, and produces local assets such as prompts, images, narration audio, slide/page files, and handoff notes.
|
||||
|
||||
It is a sibling of Writing Workbench, not a subfolder of it.
|
||||
|
||||
## Position
|
||||
## Working Model
|
||||
|
||||
```text
|
||||
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
|
||||
GPT / ChatGPT = planning, outlines, storyboards, execution packages
|
||||
User = decisions, source material, accepted planning files
|
||||
Video Workbench = project notes, execution, generated assets, handoff
|
||||
CCPE System = local work agents, runtimes, model cards, interfaces
|
||||
Skills Vault = reusable automation skills and deterministic tools
|
||||
```
|
||||
|
||||
See `PROJECTS.md` for the local project relationship map and ownership boundaries.
|
||||
Video Workbench is not the canonical home for prompts, agents, reusable automation source, deep essays, or finished article writing.
|
||||
|
||||
## Mission
|
||||
## Main Layout
|
||||
|
||||
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.
|
||||
```text
|
||||
projects/
|
||||
project-id/
|
||||
project.md
|
||||
intake/
|
||||
slides/
|
||||
slides.md
|
||||
s01/
|
||||
s02/
|
||||
|
||||
It preserves:
|
||||
handoff/
|
||||
tmp/
|
||||
garden-gpt-image-2/
|
||||
requirements/
|
||||
ccpe-consumption/
|
||||
```
|
||||
|
||||
- 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
|
||||
- `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 planning output, source notes, execution packages, 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>/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.
|
||||
- `handoff/` is for repo-level, cross-project, or context-window handoff notes.
|
||||
- `tmp/` is for local temporary files.
|
||||
- `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
|
||||
|
||||
- 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.
|
||||
- Video Workbench does not default to full video editing, image-to-video generation, or platform publishing.
|
||||
- Missing CCPE assets should be requested under `requirements/ccpe/`.
|
||||
- Missing reusable automation should be requested under `requirements/skills-vault/`.
|
||||
|
||||
## Starting A New Session
|
||||
|
||||
|
|
|
|||
|
|
@ -2,71 +2,90 @@
|
|||
|
||||
## 1. Workspace Identity
|
||||
|
||||
This project is the dimensional video output workspace.
|
||||
This project is the local execution workspace for dimensional video and slide-style output.
|
||||
|
||||
It turns deep source material into public-facing short video production packages. It is optimized for accessibility, rhythm, metaphor, visual planning, and asset preparation.
|
||||
It turns accepted GPT planning material and user-provided sources into project notes, slide/page execution folders, generated assets, and handoff material. It is optimized for practical continuation, not heavy governance.
|
||||
|
||||
## 2. Operating Principle
|
||||
|
||||
One video should usually explain one or two points.
|
||||
|
||||
The goal is not to compress a deep article into a shorter article. The goal is to extract a public-facing angle from a deep model or essay and rebuild it as a video-native experience.
|
||||
|
||||
## 3. Source Inputs
|
||||
|
||||
Typical sources:
|
||||
## 2. Collaboration Roles
|
||||
|
||||
```text
|
||||
knowledge-vault/sayings
|
||||
knowledge-vault/rules
|
||||
knowledge-vault/sources
|
||||
knowledge-vault/discussions
|
||||
writing-workbench/projects
|
||||
GPT / ChatGPT = plans, outlines, storyboards, execution packages
|
||||
User = decisions, accepted inputs, source/reference material
|
||||
Codex = project notes, file mapping, execution, local assets
|
||||
```
|
||||
|
||||
Common inputs:
|
||||
Codex should not rewrite GPT planning into duplicate project content. The accepted planning files belong in the project `intake/` directory.
|
||||
|
||||
- one long essay
|
||||
- one human-facing model document
|
||||
- selected source notes
|
||||
- Deep Research reports
|
||||
- a target audience/topic
|
||||
- optional series plan
|
||||
## 3. Project Layout
|
||||
|
||||
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.
|
||||
|
||||
Use `standalone/` when the output is a single independent video.
|
||||
|
||||
Recommended project ids:
|
||||
All video or slide-style work lives under `projects/`:
|
||||
|
||||
```text
|
||||
series/active/YYYY-MM-DD-sNNN-temp-series/
|
||||
standalone/active/YYYY-MM-DD-vNNN-temp-topic/
|
||||
projects/
|
||||
project-id/
|
||||
project.md
|
||||
intake/
|
||||
slides/
|
||||
slides.md
|
||||
s01/
|
||||
s02/
|
||||
```
|
||||
|
||||
Do not rely on final titles in folder names. Titles can evolve inside `series.md`, `episode.md`, or publishing files.
|
||||
Use root-level `handoff/` for repository-level, cross-project, series-level, or context-window handoff notes.
|
||||
|
||||
## 5. Canonical Episode Stages
|
||||
Do not split projects into `active`, `completed`, `abandoned`, `series`, or `standalone` folders. Status and series membership belong in project files because both can change during real production.
|
||||
|
||||
The workflow maps to the user's prior dimensional output process:
|
||||
If a series needs more structure, create `projects/_series/` when the first real series needs it.
|
||||
|
||||
## 4. Project Notes
|
||||
|
||||
`projects/<project>/project.md` is a lightweight Codex-maintained note. It should record:
|
||||
|
||||
- project status;
|
||||
- medium type;
|
||||
- source and reference links;
|
||||
- which `intake/` files are the outline, storyboard, execution package, or background notes;
|
||||
- current execution focus;
|
||||
- next action.
|
||||
|
||||
It should not duplicate the full outline, storyboard, shot design, or execution package.
|
||||
|
||||
## 5. Intake
|
||||
|
||||
`projects/<project>/intake/` holds material provided or accepted by the user:
|
||||
|
||||
- GPT planning documents;
|
||||
- outlines;
|
||||
- storyboards;
|
||||
- detailed slide or shot designs;
|
||||
- execution packages;
|
||||
- background notes;
|
||||
- reference images, audio notes, or source pointers.
|
||||
|
||||
File naming can be agreed during the first real project. Do not create a rigid naming scheme before the real GPT outputs are known.
|
||||
|
||||
## 6. Slides And Shots
|
||||
|
||||
Use `slides/` as the execution unit area for both video shots and PPT-style pages.
|
||||
|
||||
`projects/<project>/slides/slides.md` is the lightweight mapping and progress tracker, similar to Writing Workbench's `drafting/drafting.md`.
|
||||
|
||||
Each `slides/sNN/` folder keeps one slide, page, or shot together:
|
||||
|
||||
```text
|
||||
00-architecture = series/episode architecture, source selection, word budget
|
||||
01-proposals = three distinct angle proposals
|
||||
02-tone-outline = selected angle, core anchor, metaphor, visual style, global prompt
|
||||
03-storyboard = storyboard logic and time budget
|
||||
04-deep-production = shot-level visual plan, image prompts, voiceover, design notes
|
||||
05-assets = generated images, audio, optional video clips, asset log
|
||||
06-editing = manual edit notes and timeline plan
|
||||
07-publish = title options, description, platform copy, final script
|
||||
08-review = review notes and postmortem
|
||||
slides/
|
||||
slides.md
|
||||
s01/
|
||||
prompt files
|
||||
voiceover files
|
||||
generated images
|
||||
generated audio
|
||||
local notes
|
||||
```
|
||||
|
||||
## 6. Word Budget
|
||||
Exact file names inside `sNN/` should be chosen when that unit is executed.
|
||||
|
||||
## 7. Word Budget
|
||||
|
||||
Use the default standard:
|
||||
|
||||
|
|
@ -77,25 +96,15 @@ Use the default standard:
|
|||
|
||||
Adjust only when the user specifies a different narration speed.
|
||||
|
||||
## 7. Asset Policy
|
||||
## 8. Asset Policy
|
||||
|
||||
Image and audio generation can be automated when APIs and models are available.
|
||||
Image and audio generation can be automated when available skills or APIs are appropriate.
|
||||
|
||||
Video generation from images remains manual or semi-manual for now because output reliability varies.
|
||||
|
||||
Editing and publishing are human-controlled in the initial version.
|
||||
Editing and publishing are human-controlled unless explicitly automated later.
|
||||
|
||||
## 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
|
||||
## 9. Capability-Request Mode
|
||||
|
||||
When a required capability is missing, create a supplier ticket and pause the dependent work.
|
||||
|
||||
|
|
@ -110,7 +119,7 @@ Use `requirements/ccpe/` for local work agents, CCPE-Lite artifacts, agent specs
|
|||
|
||||
Use `requirements/skills-vault/` for deterministic automation tools, scripts, exporters, batch processors, and installable automation skills.
|
||||
|
||||
## 9. CCPE Consumption
|
||||
## 10. CCPE Consumption
|
||||
|
||||
Video Workbench consumes CCPE assets from:
|
||||
|
||||
|
|
@ -118,19 +127,6 @@ Video Workbench consumes CCPE assets from:
|
|||
C:\Users\wangq\Documents\Codex\ccpe-system
|
||||
```
|
||||
|
||||
Likely assets:
|
||||
|
||||
- Qiangge's Apprentice / dimensional output actor
|
||||
- series architect
|
||||
- angle proposal skill
|
||||
- video outline skill
|
||||
- storyboard skill
|
||||
- shot deep-production skill
|
||||
- image prompt generator
|
||||
- voiceover script generator
|
||||
- visual style model card
|
||||
- short video production runtime
|
||||
|
||||
Do not duplicate canonical CCPE definitions here. Use `ccpe-consumption/` for links, usage notes, planned dependencies, and task-specific adapters.
|
||||
Do not duplicate canonical CCPE definitions here. Use `ccpe-consumption/` for links, usage notes, planned dependencies, and future interface records.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ C:\Users\wangq\Documents\Codex\ccpe-system
|
|||
|
||||
## Policy
|
||||
|
||||
Do not copy canonical CCPE artifacts here. Record links, usage notes, and task-specific adapters only.
|
||||
Do not copy canonical CCPE artifacts here. Record links, usage notes, and future interface records only.
|
||||
|
||||
Video Workbench does not store canonical prompts, agent specs, model cards, or runtime specs. Missing CCPE capabilities should be requested through:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +1,68 @@
|
|||
# Video Workbench Context Handoff
|
||||
|
||||
This document preserves the working agreements for Video Workbench so future Codex sessions do not depend on copied chat history.
|
||||
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 = public-facing dimensional video output workspace
|
||||
CCPE System = actor, skill, model, and runtime factory
|
||||
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 video production records. It does not own canonical prompts, agent definitions, reusable automation source code, or production/business agent implementation for deployable systems.
|
||||
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.
|
||||
|
||||
## User's Dimensional Output Workflow
|
||||
## Collaboration Contract
|
||||
|
||||
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.
|
||||
```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:
|
||||
|
||||
|
|
@ -28,123 +73,9 @@ Produce a video usually under 10 minutes.
|
|||
Use about 220 Chinese characters per minute as the narration budget.
|
||||
```
|
||||
|
||||
The previous single-agent actor was named `强哥的徒弟`. Video Workbench should preserve the workflow but move toward file-based, agentic production.
|
||||
Editing and publishing remain manual unless explicitly automated later. Image-to-video remains manual or semi-manual for now.
|
||||
|
||||
## Workflow Stages
|
||||
|
||||
### Stage 0: Series Architecture
|
||||
|
||||
Decide whether the video belongs to a series or is standalone.
|
||||
|
||||
Inputs usually include:
|
||||
|
||||
- `knowledge-vault/rules` model documents
|
||||
- `knowledge-vault/sayings` essay originals
|
||||
- selected source material
|
||||
|
||||
Outputs:
|
||||
|
||||
- series plan, if any
|
||||
- episode split
|
||||
- target duration
|
||||
- word budget
|
||||
- selected source map
|
||||
|
||||
### Stage 1: Angle Proposals
|
||||
|
||||
Find three distinct entry angles.
|
||||
|
||||
Output style:
|
||||
|
||||
```text
|
||||
EP.01 [temporary episode name] - angle proposal
|
||||
```
|
||||
|
||||
The user selects the angle.
|
||||
|
||||
### Stage 2: Tone And Outline
|
||||
|
||||
Produce the video outline:
|
||||
|
||||
- framing and positioning
|
||||
- core thought anchor
|
||||
- governing metaphor
|
||||
- global visual style constraints
|
||||
- Chinese style description
|
||||
- English Global Prompt parameters
|
||||
- narration/writing protocol
|
||||
|
||||
### Stage 3: Storyboard Logic
|
||||
|
||||
Produce storyboard logic with time and word budget.
|
||||
|
||||
Example:
|
||||
|
||||
```text
|
||||
Shot 1 [Puzzle Introduction]: 30 seconds / about 110 Chinese characters.
|
||||
Shot 2 [Deep Dive]: 90 seconds / about 330 Chinese characters.
|
||||
```
|
||||
|
||||
### Stage 4: Shot Deep Production
|
||||
|
||||
For each shot, produce:
|
||||
|
||||
- page or screen visual plan
|
||||
- image generation prompt
|
||||
- voiceover script
|
||||
- design subtext
|
||||
- transition notes
|
||||
|
||||
### Stage 5: Assets
|
||||
|
||||
Generate or collect:
|
||||
|
||||
- images
|
||||
- voiceover audio
|
||||
- optional video clips
|
||||
- asset log
|
||||
|
||||
Image and audio generation can be automated later. Image-to-video remains manual for now.
|
||||
|
||||
### Stage 6: Editing
|
||||
|
||||
Editing remains manual initially.
|
||||
|
||||
Video Workbench should provide edit notes and timeline plan, not assume full editing automation.
|
||||
|
||||
### Stage 7: Publishing
|
||||
|
||||
Publishing remains manual initially.
|
||||
|
||||
Video Workbench can prepare platform copy:
|
||||
|
||||
- title options
|
||||
- description
|
||||
- cover copy
|
||||
- hashtags / tags
|
||||
- final script
|
||||
|
||||
## Project Shape
|
||||
|
||||
Use `series/` for multi-episode work and `standalone/` for one-off videos.
|
||||
|
||||
Each episode should preserve both process and final outputs. The canonical expanded episode structure is in:
|
||||
|
||||
```text
|
||||
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
|
||||
## 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +0,0 @@
|
|||
# Active Episodes
|
||||
|
||||
No active standalone episodes yet.
|
||||
|
||||
Record:
|
||||
|
||||
- episode id
|
||||
- temporary title
|
||||
- source-map path
|
||||
- current stage
|
||||
- duration target
|
||||
- next action
|
||||
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Active Series
|
||||
|
||||
No active series projects yet.
|
||||
|
||||
Record:
|
||||
|
||||
- series id
|
||||
- temporary title
|
||||
- source model / essay
|
||||
- episode count
|
||||
- current episode
|
||||
- next action
|
||||
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Completed Videos
|
||||
|
||||
No completed videos yet.
|
||||
|
||||
Record:
|
||||
|
||||
- episode id
|
||||
- final title
|
||||
- source article/model
|
||||
- final script path
|
||||
- asset paths
|
||||
- publish status
|
||||
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Source Article Map
|
||||
|
||||
This index maps video outputs back to Knowledge Vault sources.
|
||||
|
||||
Record:
|
||||
|
||||
- video or episode id
|
||||
- source essay path
|
||||
- source model path
|
||||
- source notes or research
|
||||
- extracted point
|
||||
- resulting package path
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
|
||||
|
|
@ -1 +0,0 @@
|
|||
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
# Angle Proposal
|
||||
|
||||
## Source
|
||||
|
||||
## Audience
|
||||
|
||||
## Duration Target
|
||||
|
||||
## Proposal 1
|
||||
|
||||
## Proposal 2
|
||||
|
||||
## Proposal 3
|
||||
|
||||
## Recommended Selection
|
||||
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
# Asset Log
|
||||
|
||||
## Images
|
||||
|
||||
## Audio
|
||||
|
||||
## Video Clips
|
||||
|
||||
## Uploads
|
||||
|
||||
## Notes
|
||||
|
||||
|
|
@ -1,55 +0,0 @@
|
|||
# Episode Project Structure
|
||||
|
||||
Use this structure when expanding a standalone video or a series episode.
|
||||
|
||||
```text
|
||||
ep-01-temp-title/
|
||||
episode.md
|
||||
source-map.md
|
||||
|
||||
00-architecture/
|
||||
series-context.md
|
||||
episode-scope.md
|
||||
word-budget.md
|
||||
|
||||
01-proposals/
|
||||
proposal-v1.md
|
||||
selected-angle.md
|
||||
|
||||
02-tone-outline/
|
||||
video-outline.md
|
||||
global-visual-style.md
|
||||
global-prompt.md
|
||||
narration-protocol.md
|
||||
|
||||
03-storyboard/
|
||||
storyboard-logic.md
|
||||
|
||||
04-deep-production/
|
||||
shots/
|
||||
shot-01.md
|
||||
shot-02.md
|
||||
voiceover-full.md
|
||||
image-prompts.md
|
||||
design-notes.md
|
||||
|
||||
05-assets/
|
||||
images/
|
||||
audio/
|
||||
video-clips/
|
||||
asset-log.md
|
||||
|
||||
06-editing/
|
||||
edit-notes.md
|
||||
timeline-plan.md
|
||||
|
||||
07-publish/
|
||||
title-options.md
|
||||
description.md
|
||||
platform-copy.md
|
||||
final-script.md
|
||||
|
||||
08-review/
|
||||
review-notes.md
|
||||
```
|
||||
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
# Episode
|
||||
|
||||
## Identity
|
||||
|
||||
- Episode ID:
|
||||
- Temporary title:
|
||||
- Final title:
|
||||
- Series:
|
||||
- Status:
|
||||
- Target duration:
|
||||
- Word budget:
|
||||
|
||||
## Source Point
|
||||
|
||||
## Public-Facing Question
|
||||
|
||||
## Selected Angle
|
||||
|
||||
## Human Decision Gates
|
||||
|
||||
## Notes
|
||||
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
# Publish Copy
|
||||
|
||||
## Title Options
|
||||
|
||||
## Description
|
||||
|
||||
## Cover Copy
|
||||
|
||||
## Tags
|
||||
|
||||
## Platform Variants
|
||||
|
||||
|
|
@ -1,25 +0,0 @@
|
|||
# Series Project Structure
|
||||
|
||||
Use this structure when expanding a new active series.
|
||||
|
||||
```text
|
||||
YYYY-MM-DD-sNNN-temp-series/
|
||||
series.md
|
||||
source-map.md
|
||||
episode-map.md
|
||||
|
||||
episodes/
|
||||
ep-01-temp-title/
|
||||
episode.md
|
||||
source-map.md
|
||||
00-architecture/
|
||||
01-proposals/
|
||||
02-tone-outline/
|
||||
03-storyboard/
|
||||
04-deep-production/
|
||||
05-assets/
|
||||
06-editing/
|
||||
07-publish/
|
||||
08-review/
|
||||
```
|
||||
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
# Series
|
||||
|
||||
## Identity
|
||||
|
||||
- Series ID:
|
||||
- Temporary title:
|
||||
- Final title:
|
||||
- Status:
|
||||
- Created:
|
||||
- Last updated:
|
||||
|
||||
## Source Model Or Essay
|
||||
|
||||
## Series Thesis
|
||||
|
||||
## Target Audience
|
||||
|
||||
## Episode Plan
|
||||
|
||||
## Notes
|
||||
|
||||
|
|
@ -1,19 +0,0 @@
|
|||
# Shot
|
||||
|
||||
## Shot Identity
|
||||
|
||||
- Shot number:
|
||||
- Function:
|
||||
- Time budget:
|
||||
- Word budget:
|
||||
|
||||
## Visual Plan
|
||||
|
||||
## Image Prompt
|
||||
|
||||
## Voiceover
|
||||
|
||||
## Design Subtext
|
||||
|
||||
## Transition Notes
|
||||
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
# Source Map
|
||||
|
||||
## Knowledge Vault Sources
|
||||
|
||||
## Source Essay
|
||||
|
||||
## Source Model
|
||||
|
||||
## Selected Excerpts
|
||||
|
||||
## CCPE Sources
|
||||
|
||||
## Notes
|
||||
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
# Storyboard Logic
|
||||
|
||||
## Duration Target
|
||||
|
||||
## Word Budget
|
||||
|
||||
## Shots
|
||||
|
||||
### Shot 1
|
||||
|
||||
- Function:
|
||||
- Time budget:
|
||||
- Word budget:
|
||||
- Logic:
|
||||
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
# Video Outline
|
||||
|
||||
## Framing And Positioning
|
||||
|
||||
## Core Thought Anchor
|
||||
|
||||
## Governing Metaphor
|
||||
|
||||
## Global Visual Style
|
||||
|
||||
## English Global Prompt Parameters
|
||||
|
||||
## Narration Protocol
|
||||
|
||||
## Outline
|
||||
|
||||
Loading…
Reference in New Issue