Jarvis command center · Interactive wireframe

Jarvis command center Wireframe · v1

Interactive concept. Sample tasks and machines; no live actions.

Why this layout

Work leads. Decisions that need the user sit above running tasks. Every row carries its project and execution machine. Opening task details does not change the command target.

One command destination. The composer names machine, project, and task together. Voice and text share that target. Ambiguity pauses the request; disconnection preserves it without moving work.

Machines have their own page. Online/offline, account access, and capability preset are separate. At the limit, the user chooses a replacement and sees the consequence before applying it.

Readiness is explicit. Setup walks through the existing install, account, connection, provider, and voice flows. Full, Controller, and Headless keep their defined roles. Setup is a view over those owners.

Implementation contract and mobile behavior

Use the existing task shell events and typed Jarvis command state. Keep the list bounded; load details on demand. No new report ledger or periodic task polling.
Use node-qualified ProjectRef and TaskRef values for row keys, targets, approvals, cancellations, and disconnect recovery. Show cached detail as last-known state when a node is unavailable.
Keep deterministic clarification and confirmation in the existing runtime. A preview, highlighted row, or natural-language reply never authorizes a tool call.
Account policy must arrive from the relay with a typed mutation result. Enforce the cap atomically and return the affected machine identities. Do not duplicate the cap in UI code.
Voice readiness needs an account entitlement and session owner as well as local capture readiness. Display BYOK/cloud choice only when supported. The sample quota here is descriptive, not a proposed price plan.
On a phone, collapse the machine summary into navigation and use one column. Mirror the same task, target, clarification, and connection states in the separate React Native client.
Task cancellation and voice stop are separate actions. Revoking account access must describe whether existing sessions are actually closed. That contract needs resolution before shipping the Devices toggle.

Designed from PR #16 at 631bb623, with the #15 cloud voice follow-up represented as proposed UI. All sample completions, provider readiness, and setup statuses are illustrative.