Video

Video at /video is the tenant’s AI video-creation surface: describe what to make, generate. Past generations persist in the History rail; the composer makes new ones. Still imagery starts at Images; this surface is where video outputs live.

• The History rail lists past generations with thumbnail, duration-plus-model line, status, and date per entry. History is where re-runs start — check it before regenerating what already exists.
• The preview pane starts empty until prompted. The text-to-video composer carries a model picker with resolution and duration controls. Treat the product UI as the source of truth for the models your tenant offers.
• A generated video attached to nothing is decoration; attached to a work item, it is evidence on the record. The record a file attaches to is the source of truth about that work.

• Describe the deliverable, not the vibe. A prompt that names the use survives review; a mood without a use gets regenerated.
• Source files and exports live under Files: this surface is the working view, the file store is the evidence. Tag on upload, not later.
• Repeatable video shapes belong in Templates. If the same format gets rebuilt every engagement, the template should exist.

What next

• Images: the still-imagery sibling surface.
• Deliverables: the client-facing outputs video serves.
• Files: the file store behind video artifacts.
• Templates: repeatable video shapes.