Good evening, operator.
Your publishing system is ready. Connect services to move from control plane to autonomous operations.
Recent activity
Command center
Ask JARVIS to plan, explain or prepare work. Destructive actions always require an explicit approval step.
Awaiting instruction
Your command result will appear here. AI calls are real and may require platform credits.
Trend radar
Collect, normalize and score current signals without copying other creators.
No live signals yet
Connect a source, then run collection from your worker service. Trend score will show configured indicators—not a promise of performance.
Content studio
Create a research-aware brief with the configured AI copilot, then pass it to your backend pipeline for production.
Start with a clear angle
Production brief
Add a topic to produce a structured brief. The result is saved only when you choose to keep it.
Video queue
Every long-running task belongs in a worker queue and keeps its real status.
Published
Video IDs, visibility and performance belong here after a real YouTube upload.
No published videos recorded
Connect YouTube and upload through the official API. This view will never show made-up performance.
Analytics
Only authorized YouTube Analytics data is shown. Estimates and hypotheses are labeled separately.
Analytics unavailable
Connect a YouTube channel with Analytics scope to retrieve real views, watch time, subscriber changes and revenue availability.
Connections
Credentials belong in your backend environment, never in this browser surface. Use the checklist to configure real integrations.
YouTube
OAuth 2.0, uploads and Analytics API
Telegram
Owner bot notifications and approvals
AI copilot
Platform text model for planning and briefs
Required backend variables
Automation
These safeguards persist locally as operator intent. A backend worker must enforce them before any external action.
Allow scheduled workers to prepare content.
Never enables itself; requires a connected backend and channel.
Hold every output for owner review before upload.
Stop new work and publishing while keeping recoverable jobs.
Daily limits
Schedules
Scheduling requires a persistent worker service. Define intent here, then sync it through the backend API.
No worker schedules synced
Once the scheduler API is connected, recurring and one-time jobs will appear here with timezone and idempotency details.
Knowledge base
These brand rules are used by the local copilot prompt and can be synced to your backend later.
System health
Statuses are derived from this runtime and saved workspace state. External services remain unknown until the backend reports health.
A green frontend status does not mean YouTube or workers are healthy. Each dependency needs an explicit server-side check.
Logs
Operator-visible events from this control plane. Server logs should remain the source of truth in production.
Security
JARVIS keeps browser state separate from credentials. Production authorization must be enforced by the backend.
Secrets stay server-side
OAuth refresh tokens, Telegram bot tokens, provider keys and session secrets must never be placed in frontend storage.
Policy activePublishing is gated
Manual approval is the safe default. A server-side policy must re-check role, fact check, originality, budget and emergency stop.
Backend requiredActions are auditable
The local trace records operator intent. Production audit events should include user, job, provider, request ID and outcome.
Ready