You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.1 KiB
1.1 KiB
Decision 0003: Video Parameter Ownership
Status: Accepted Date: 2026-05-03
Context
GenerateVideoNodeData currently stores provider-specific values mostly under parameters. Product UI wants common controls such as aspect ratio, resolution, duration, fps, and sound.
Different providers may name those fields differently. For example, one provider may call duration seconds, another duration_seconds.
Decision
Semantic video controls should become first-class node fields. Provider-specific controls remain in parameters.
First-class fields to add before exposing fixed video controls:
aspectRatioresolutiondurationSecondsfpssoundEnabled
Executors map first-class fields to provider payload names.
Rationale
The composer needs stable fields for common controls. Provider schemas are still useful, but they should not define the product's core video editing model.
Consequences
- MVP can ship prompt/model/references/status plus schema-driven advanced controls first.
- Fixed video controls must wait until the data model and executor mapping are implemented.
- Provider-only options stay under
parameters.