Video Studio — per-clip deep engine host (E4d)

Video

E4c made the Image Studio the deep host of the shared media engine. E4d brings the same pattern to the Video Studio — but per clip. Each clip in Stage-4 now hosts a composed-prompt GeneratePanel (Higgsfield-only model picker · editable composed video prompt · guide · refine-with-history · pinned snapshot) and an actionable ResourceChecklist (start/end frame · image · video · audio roles) that replaces the old bespoke ingredient list. The takes grid + Generate-clip row stay unchanged below — coexistence, not replacement. Pink studio chrome hosts a distinct #7c3aed engine card inside each ClipCard. Light app theme · clickable. No caching — refresh for latest.

Pink studio chrome
The Video Studio's own shadcn surface — the clip rail, the ClipCard, the stepper, the shots editor, model & settings, the takes grid and the Generate-clip row. Unchanged in E4d. This is the host.
The #7c3aed engine card
The shared media engine (gua-*) — the composed-prompt GeneratePanel + the ResourceChecklist — mounted inside the pink ClipCard as a deliberate, contained seam. Same engine as Image Studio E4c, scoped to one clip.
What changed in E4d. Each clip now hosts the shared media engine. (a) A new composed per-clip prompt — a Higgsfield-only ProviderModelPicker + editable composed VIDEO prompt + guide + refine-with-history (Revert) + scope badge — gated DISABLED until a model is picked for the clip, then pinned to a per-clip snapshot so Generate-clip runs exactly that prompt. (b) The old "Reference ingredients" block is replaced by an actionable per-clip ResourceChecklist — video roles (start frame · end frame · image · video · audio) driven by frames-vs-ingredients mode, with Have/Needed/Generating rows, a per-row ⚡ on-platform / ✦ DIY toggle, an inline ResourceGenerator + candidate grid + "Use this", and Pick/Replace. The shots editor, takes grid and Generate-clip row stay unchanged below — coexistence. Provider-key boundary: compose & refine ride the free text path; per-clip / per-resource Generate resolves creds via resolveMediaProviderKey and spends a media credit — never the platform key. Recursion stays flat: a generated resource fills its own node, never a nested checklist.
Pages — Summer Sale · 15s Reel example
00
Design system
The two surfaces side by side: the pink studio atoms (.card, .btn/.btn.accent, .section-h, takes grid) and the #7c3aed engine atoms (.epanel, .pchip, .ptextarea, .rhist, .reschecklist/.resrow). The contract for the seam.
Open
01
Per-clip work (overview)
The new ClipCard ordering end-to-end: left clip rail + the evolved right card. The composed-prompt GeneratePanel and the per-clip ResourceChecklist mount inside the pink chrome; shots, takes and Generate-clip stay below — one clip hosting the whole engine.
Flagship Open
02
Composed prompt panel
The per-clip GeneratePanel in detail: a Higgsfield-only ProviderModelPicker, an editable composed VIDEO prompt + guide + scope badge — shown gated DISABLED until a model is picked, then live once it is.
Open
03
Refine & pin to clip
Chat-refine the composed prompt on the free text path, with a .rhist history you can Revert to any turn. The refined prompt pins to a per-clip snapshot so Generate-clip runs exactly that text — the engine and the takes grid stay in sync.
Open
04
Resource checklist (video)
The actionable ResourceChecklist that replaces "Reference ingredients" — video roles (start frame · end frame · image · video · audio) driven by frames-vs-ingredients mode, Have/Needed/Generating rows, per-row ⚡/✦ toggle, inline ResourceGenerator + candidate grid + "Use this", Pick/Replace.
Open
05
Flat recursion
The key invariant, made visible for video: generating a clip resource (a start frame, a VO…) fills its own node and stops — it does not spawn a fresh required-resources checklist inside itself. One level, always.
Open
06
Config spec round-trip
How the clip-level ConfigStage spec (mode · model · roles) feeds the per-clip engine, and how the pinned snapshot + filled resources round-trip back into the clip's config — so the ClipCard and the spec never drift.
Open
The seam. Every page keeps the Video Studio's pink shadcn chrome (clip rail, ClipCard, shots, takes, Generate-clip) hosting the gua-* #7c3aed engine — the composed-prompt GeneratePanel and the actionable ResourceChecklist — as a deliberate, contained seam, exactly like Image Studio E4c. Start at Per-clip work (overview) for the full ClipCard, then drill into the panel, refine/pin, and the checklist.