Creative Studio

The shared vids-operator desktop worker, its registry entries, and the oshal-vids CLI stay framework-resident; the /api/vids surface it tiles is owned by the vids app (declared dependency); this package is the manifest + tools + tile over them.

• Produce the next story video. Make the next unproduced kid-safe story video: rotate the library (fables / fairytales / famous sayings), animate the ~100-word story across ~10 continuous Google Vids EXTEND scenes on the…
• Produce a specific story video. Animate a specific story across ~10 continuous Extend scenes in Google Vids and save it. Pass a library storyId (e.g
• List produced story videos. Read back the dispatched story/clip jobs and their status (from the vids_jobs ledger). The node's own `oshal-vids story --list` reads the content-folder manifests directly

1. 01

   You open it, or the assistant does

   Opening ?app=creative-studio loads its 4 screens into the shared cockpit, starting on creative-studio. The ribbon, the ticket list and the assistant are already there — the app contributes views, not a second application to log into.

2. 02

   Or you just ask

   The assistant classifies what you asked for and hands it to the bot that owns that domain. You do not pick the app, and you do not learn a command — routing is by declared capability, not by keyword matching a menu.

3. 03

   A named bot picks it up

   vids-operator is accountable for the work. 4 declared capabilities say what it is trusted to do; the tokens and dollars it spends are recorded against that identity, so the cost has a line item rather than disappearing into a monthly bill.

4. 04

   Longer work becomes a ticket

   Scheduled and swarm-initiated work enters the queue as a creative-story ticket. It is durable, it has an owner, you can watch it move through its phases, and if it fails it fails somewhere you can open and read.

5. 05

   The result lands where you can check it

   Back on the app's own screens, as state you own — not as a chat message you have to scroll back to find.

• Routing is by declared capability, not by keyword. vids-operator advertises what it is accountable for, and the assistant matches against that.
• Asks that land here: anything about veo prompt craft, anything about vids generate, anything about vids operate, anything about shot planning.
• The specialist does the work, not the assistant. Cost, permissions and audit stay attached to the bot above — delegation does not launder accountability.
• It will tell you when it cannot. If a request needs your screen — an approval, a payment, a login — it says which app to open rather than guessing.

• Other apps: Vids Studio. Install is dependency-aware and refuses to orphan them.

All 11 creative apps →