Spec round-trip & the two AI primitives

Image

How the media-request's generationSpec flows in and out of the Studio, and why authoring direction and composing the prompt stay two distinct AI calls.

Shared media engine

generationSpec round-trip

scope: this media-request

Pre-fill

The media-request's generationSpec seeds the panel (initialSpec) — provider, model, last composed prompt — so re-opening the Studio resumes where you left off.

Compose & refine

Preview composes the prompt from your direction; each Refine chains off the current prompt (basePrompt) on the cheap text path and is recorded in history with Revert.

Write-back

Generating persists the composed/refined prompt into the production and writes the full spec back to the request (provider / model / prompt). The worker stamps an as-generated prompt snapshot, shown read-only on Deliver.

Prompt composed by your AI provider; delivered by your media connector.

Two AI primitives, kept distinct

Brief and Generate each make their own AI call. One authors the structured direction; the other turns that direction into the final generation prompt. Keeping them separate is what makes the round-trip above resumable.

✍️ Draft with AI (Brief)

Authors the structured direction inputs — visual concept, colour / mood, layout, overlays.

Stage 1 · Brief & direction

✨ Compose / Refine (Generate)

Produces the final generation prompt from those inputs — preview, refine, generate.

Stage 2 · Generate

requiredResources stay a read-only checklist in E4b. Per-resource generation — turning each needed asset into its own production from the panel — arrives in E4c.