Studio Signal consultant
Plan by text or start a reviewed live voice session through the protected AI Gateway route.
Live voice consultant
Model: openai/gpt-realtime-2 · browser auto-stops after two minutes
Ready for review. Microphone is off.
Today / Studio command
Plan by text or start a reviewed live voice session through the protected AI Gateway route.
Model: openai/gpt-realtime-2 · browser auto-stops after two minutes
Ready for review. Microphone is off.
Every role feeds a single reviewable output.
Useful progress, without fake status lights.
Jarvis, research, creative work, and approvals all land in one place.
Adding a request creates a local draft only. No generation, upload, message, or payment is triggered.
The useful core of the “AI marketing team” concept—split into accountable, reviewable roles.
Collect trusted sources, then turn the question into a brief. This interface does not search the web or open links by itself.
Build target: a private research agent that returns source links, summaries, and a confidence note. Until an approved search provider is linked, this page is a source-review board—not “live web access.”
Use reviewed sources to make the next job precise.
Formats and production goals are ready. Real YouTube numbers appear only after a read-only connection.
A channel is not “connected” until Fahim approves Google’s access request.
Videos, views, subscribers, and publishing cadence.
Hook, retention markers, format, and next experiment.
What the channel needs next—not made-up trend data.
Draft queue before any upload or public post.
Turn one brief into an original hook, script, scene list, voice direction, and rights check.
Model: openai/gpt-6-luna
Waiting for a brief.
Make a production brief that can travel from research to script to scenes to approval.
One job has a visible path: research → script → scenes → assets → review. Every later connected service must return its output and cost back to that same job.
What a completed brief contains.
Move work forward only as a draft or review artifact.
Create one original visual after reviewing the model and per-image charge.
Render one 4-second original clip through the protected AI Gateway route after a cost review.
Four lanes for the visual workflows in the reels—kept behind provider, cost, and rights checks.
Prompt packs, art direction, model choice, and image/video render jobs attached to one brief.
Environment changes, motion briefs, and scene continuity—without claiming a provider is already connected.
Create a consistent original fictional avatar or animated character kit for a channel, with clear disclosure and review.
Voice direction, original narration, and licensed/original music planning attached to each scene list.
What prevents “generate and hope” from becoming the process.
Confirm character, voice, music, and reference rights.
Display provider, credits, and expected output before render.
Review consistency, claims, audience fit, and policy.
Save source, prompt version, asset status, and next action.
These are the real departments behind the “zero employees” reel. Today they are configured roles, not hidden autonomous workers.
Agents can prepare work. Publishing, inbox replies, direct messages, paid generations, and account changes remain human-approved.
A future worker can process already-approved research or drafting jobs on a schedule. It must be visible in the queue, limited by cost, logged, retry-safe, and unable to publish or message anyone without an explicit final approval.
Every draft needs a clear human decision before it can become a paid render, scheduled upload, or public message.
Marking a job ready here does not publish it. It only records that it is prepared for Fahim’s review. Uploading and scheduling stay separately disabled until exact account permissions are approved.
A small checklist to prevent surprise cost or rights issues.
Every integration starts with the smallest safe permission. None are connected from this dashboard.
Connection buttons are intentionally not OAuth buttons. A real connection needs a server-side credential vault, provider approval, a tested callback, scope review, error handling, and a live health check.
The flow that turns a planned tile into a trusted connection.
Save explicit facts, preferences, and project decisions. Chat is not memorized automatically.
Only facts Fahim saves here become memory records. The consultant does not silently ingest private conversations. Records are tied to the signed-in studio owner and can be edited or deleted.
Save repeatable text-drafting recipes. Run one on demand after reviewing the model and usage.
Recipes persist and can generate a reviewed text draft through AI Gateway. Daily/weekly labels are plans, not background jobs. This deployment has no connected scheduler; it will not run while the dashboard is closed. No media, publishing, or account actions run from a recipe.
Private uploads and generated media live here with their origin and model recorded.
Uploaded or generated assets are private workspace files. Saving an asset does not upload it to YouTube or grant rights to a character, voice, image, or soundtrack.
Plan production and review dates across channels. This does not publish to YouTube.
These are internal production dates only. YouTube and other platform publishing remain disconnected and require a separate account connection and final approval.