The connecting idea

One generation unit — Create & the Studios share it

The same unit makes any media resource, the same way everywhere. Only the mode differs: get a prompt & do it yourself, or generate on-platform.

Anatomy

1 · Mode✦ prompt / ⚡ on-platform→ 2 · ProviderFlow / Higgsfield→ 3 · Methodframes / ingredients→ 4 · Model + configcapability-driven→ 5 · Outputprompt+guide / takes

Two audiences, one unitthe only difference is the mode toggle

✦ Prompt & direction (DIY)

For people using their own tool (Google Flow, Higgsfield, OpenArt).

✓ Model-aware generation prompt

✓ Step-by-step guide for the chosen platform

✓ Required-resources checklist

✓ Upload the result back → becomes the post hero

⚡ Generate on-platform

For people who want it made here (Higgsfield connector).

✓ Same prompt, generated for you

✓ Live status → takes

✓ Pick a take → becomes the post hero

v1 ships ✦ prompt first (Flow + Higgsfield); ⚡ on-platform + deep iteration land with the Studios.

Resources are sub-generationsuniform, top to bottom

🎬 Reel — “the retainer pitch” · ✦ or ⚡

🖼 First-frame image

🖼 Last-frame image

🧪 Ingredient: founder have

🎞 Office b-roll clip

Each resource is the same unit — choose prompt or on-platform for it too. v1 = flat: the checklist gives a prompt+guide per resource; deep per-resource generation lives in the studio.

How Create and the Studio connect

Create (compact)

decide → prompt / kickoff → status. Finish a simple post here.

⇄

media-request
· generationSpec ·

source of truth: mode · provider · model · method · config · prompt · resources

⇄

Studio (deep)

same unit + iteration + the resource tree. Pre-filled from the spec; overrides write back.

No duplicated logic — both hosts render the one engine and read/write the same request. Delivered media flows back to the post hero via the existing deliver path.

Default mode

Default media mode for this brand

Set in Social settings · overridable on every resource.

✦ Prompt⚡ On-platform