Sync latest TrueGrowth updates
This commit is contained in:
jiam
@@ -0,0 +1,101 @@
|
||||
## ADDED Requirements
|
||||
### Requirement: VideoAgent Primary Runtime
|
||||
The AI clip workbench SHALL submit new customer-facing clip tasks to `videoagent-local` instead of `funclip-local`.
|
||||
|
||||
#### Scenario: User submits a new clip job
|
||||
- **WHEN** the user submits a configured AI clip job
|
||||
- **THEN** the created task uses provider id `videoagent-local`
|
||||
- **AND** customer-facing UI does not mention FunClip, VideoAgent, CUDA, model paths, or command-line details
|
||||
|
||||
### Requirement: Intent-First Clip Workflow
|
||||
The AI clip workbench SHALL begin with source media and a natural-language production goal rather than a fixed list of clip presets.
|
||||
|
||||
#### Scenario: User defines the desired output
|
||||
- **WHEN** the user selects source media and enters a goal such as turning a long course into short clips
|
||||
- **THEN** the page captures the source, goal, business scene, platform format, and desired output package before task submission
|
||||
|
||||
### Requirement: Simplified First-Screen Monitor
|
||||
The AI clip workbench SHALL present the first screen as a prompt-led work area with a single video monitor on the right.
|
||||
|
||||
#### Scenario: User has not selected media
|
||||
- **WHEN** the user opens the first screen without selected media
|
||||
- **THEN** the right-side monitor shows only two primary source actions: choose from the asset center or upload a local file
|
||||
- **AND** the visible flow does not show the legacy capability-template wall
|
||||
|
||||
#### Scenario: User selects media
|
||||
- **WHEN** the user chooses a video source
|
||||
- **THEN** the right-side monitor previews the selected video and keeps source replacement inside the monitor controls
|
||||
|
||||
### Requirement: Workflow-Aware Multi-Source Inputs
|
||||
The AI clip workbench SHALL choose the source input model from the selected workflow rather than assuming every job is a single-video trim.
|
||||
|
||||
#### Scenario: User chooses a single-primary workflow
|
||||
- **WHEN** the user selects workflows such as transcript editing, auto captions, summary Q&A, course chapters, interview Q&A, or talking-head cleanup
|
||||
- **THEN** the page requires one primary video or audio source
|
||||
- **AND** optional reference media stays secondary and does not replace the primary monitor preview
|
||||
|
||||
#### Scenario: User chooses a multi-source workflow
|
||||
- **WHEN** the user selects workflows such as multi-source montage, script-to-video, B-roll planning, platform packaging, or batch processing
|
||||
- **THEN** the page allows multiple image, video, and audio assets from the asset center or local upload according to that workflow
|
||||
- **AND** the submitted payload identifies primary source, supporting sources, source mode, accepted media types, and cardinality
|
||||
|
||||
### Requirement: Shared Asset Center Picker
|
||||
The AI clip workbench SHALL reuse the shared asset center picker for source selection.
|
||||
|
||||
#### Scenario: User chooses from asset center
|
||||
- **WHEN** the user clicks the source monitor asset-center action
|
||||
- **THEN** the shared asset center modal opens with existing media browsing, preview, upload, delete, and multi-select behavior
|
||||
- **AND** generated works from other TrueGrowth modules are available as selectable assets when they have a valid media URL
|
||||
|
||||
### Requirement: Quick Scenarios Configure The Job
|
||||
The AI clip workbench SHALL expose practical quick scenarios based on supported clip-workbench abilities and mainstream AI editing workflows.
|
||||
|
||||
#### Scenario: User clicks a quick scenario
|
||||
- **WHEN** the user selects a quick scenario such as long-video highlights, transcript editing, course chapters, interview Q&A, ecommerce live clips, auto captions, publish packaging, source montage, or script-to-video planning
|
||||
- **THEN** the page fills the production goal and updates clip count, duration, platform, subtitle, speaker, context, title, publishing, batch, and regrouping options where applicable
|
||||
|
||||
#### Scenario: Capability is not first-version ready
|
||||
- **WHEN** a VideoAgent demo ability depends on advanced voice conversion, singing, music-video generation, or semantic retrieval models that are not connected through the current TrueGrowth model center
|
||||
- **THEN** the ability is not shown as a first-screen quick scenario
|
||||
- **AND** the service check or model center may show it as an optional future capability without blocking the basic clip workflow
|
||||
|
||||
### Requirement: Structured Clip Plan And Deliverables
|
||||
The AI clip workbench SHALL display a structured AI plan and generated deliverables for each submitted task.
|
||||
|
||||
#### Scenario: Task returns a plan
|
||||
- **WHEN** a clip task is running or complete
|
||||
- **THEN** the page shows the planned steps, transcript or draft transcript, candidate segments with reasons, timeline items, and deliverables such as SRT, title, cover prompt, publish copy, and video assets when available
|
||||
|
||||
#### Scenario: Adapter returns only structured deliverables
|
||||
- **WHEN** the local adapter can generate a plan, transcript, segments, timeline, and publishing deliverables but has not rendered a playable video file
|
||||
- **THEN** the task completes with structured result metadata and no generated video asset id
|
||||
- **AND** the asset center does not receive an unplayable placeholder video or JSON plan asset
|
||||
- **AND** the UI offers result editing from the structured task result without implying a playable video exists
|
||||
|
||||
### Requirement: Capability Package Readiness
|
||||
The local runtime SHALL report customer-facing readiness for basic clipping, video understanding, creative remaking, and voice/audio processing packages.
|
||||
|
||||
#### Scenario: User opens service check
|
||||
- **WHEN** the user opens the clip workbench service check dialog
|
||||
- **THEN** the page shows package readiness as available, preparing, or needs initialization without exposing third-party technical names
|
||||
|
||||
### Requirement: Model Center Reuse
|
||||
The AI clip runtime SHALL reuse existing TrueGrowth model-center and digital-human capabilities before requesting VideoAgent-specific model downloads.
|
||||
|
||||
#### Scenario: Existing local models can satisfy a clip capability
|
||||
- **WHEN** the model center already has usable ASR, voice, image/video, or digital-human models
|
||||
- **THEN** clip readiness counts those models as reusable for transcription, voice, B-roll planning, or digital-human handoff
|
||||
- **AND** the customer does not need to download duplicate Whisper, CosyVoice, fish-speech, or digital-human model packages for the same first-version function
|
||||
|
||||
#### Scenario: Optional advanced model is missing
|
||||
- **WHEN** ImageBind, Seed-VC, DiffSinger, or similar advanced packages are not present
|
||||
- **THEN** first-version quick scenarios remain available for plan, transcript, segment, montage, and publish deliverables
|
||||
- **AND** advanced semantic search, voice conversion, or music-video workflows are presented only as optional initialization from the model center
|
||||
|
||||
### Requirement: Legacy FunClip Migration Fallback
|
||||
The system SHALL preserve existing FunClip task history while preventing FunClip from defining the new customer-facing clip workflow.
|
||||
|
||||
#### Scenario: User has older clip tasks
|
||||
- **WHEN** the task history contains older `funclip-local` records
|
||||
- **THEN** the history can still display them as clip workbench tasks
|
||||
- **AND** new submissions use `videoagent-local`
|
||||
Reference in New Issue
Block a user