JARVIS/Dashboard

Control plane ready

↻

OOwner

Operations overview

Good evening, operator.

Your publishing system is ready. Connect services to move from control plane to autonomous operations.

+Open command center

Production bridge not connected

Metrics, OAuth, queues, rendering and publishing stay safely unavailable until your backend bridge is configured. No numbers are fabricated.

Configure

Pipeline

Content lifecycle

Awaiting bridge

Stages become live when the worker API is connected.

Trace

Recent activity

View logs

Natural language control

Command center

Ask JARVIS to plan, explain or prepare work. Destructive actions always require an explicit approval step.

What should JARVIS do?

AI can propose actions; the control plane enforces permissions.Run command→

Operator response

Awaiting instruction

Live

↯

Your command result will appear here. AI calls are real and may require platform credits.

Signal intelligence

Trend radar

Collect, normalize and score current signals without copying other creators.

↻Refresh signals

RegionCategory

Live source connection required

The radar will only display signals returned by your configured YouTube or search provider. This workspace never invents trend scores.

Connect source

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.

Creative production

Content studio

Create a research-aware brief with the configured AI copilot, then pass it to your backend pipeline for production.

Brief builder

Start with a clear angle

Safety checked

Topic or source signal

LengthFormat

AudienceExtra guardrails OptionalGenerate production brief→

Copilot output

Production brief

Not saved

✦

Add a topic to produce a structured brief. The result is saved only when you choose to keep it.

Save briefDiscard

Execution pipeline

Video queue

Every long-running task belongs in a worker queue and keeps its real status.

0items

AllActiveReviewFailed

Verified outputs

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.

Set up YouTube

Measured 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.

Actual metricsNot available

RevenueUnavailable through current authorization

Connect YouTube

Provider gateway

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

Not connected

ChannelNot configured

View setup requirements

Owner bot notifications and approvals

Not connected

Owner chatNot configured

View setup requirements

AI copilot

Platform text model for planning and briefs

Checking

ModelDetecting runtime…

Test AI copilot

Deployment checklist

Required backend variables

Copy names

Never paste secrets into the browser app or commit them to Git. The backend should encrypt OAuth tokens at rest and keep provider keys server-side.

Policy controls

Automation

These safeguards persist locally as operator intent. A backend worker must enforce them before any external action.

Autonomous mode

Allow scheduled workers to prepare content.

Automatic publishing

Never enables itself; requires a connected backend and channel.

Require approval

Hold every output for owner review before upload.

Emergency stop

Stop new work and publishing while keeping recoverable jobs.

Stop all automationResume

Guardrails

Daily limits

Local policy

Maximum videos per dayMaximum AI spend per day (credits)Default regionSave policy

Production enforcement reminder

Local toggles do not call YouTube, Telegram, queues or FFmpeg. Your backend must re-check role, budget, approval and emergency-stop state on every job.

Timing and cadence

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.

Review connections

Persistent creative memory

Knowledge base

These brand rules are used by the local copilot prompt and can be synced to your backend later.

Brand namePrimary niche

Target audienceWriting and voice styleForbidden topics or claimsPreferred CTA

Stored in isolated app storage on this device.Save knowledge

Runtime observability

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.

Structured trace

Logs

Operator-visible events from this control plane. Server logs should remain the source of truth in production.

Clear local trace

TimeLevelEventSource

Trust boundary

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 active

Publishing is gated

Manual approval is the safe default. A server-side policy must re-check role, fact check, originality, budget and emergency stop.

Backend required

Actions are auditable

The local trace records operator intent. Production audit events should include user, job, provider, request ID and outcome.

Ready