Mission Control from SOL 1

What this means for you

Rover is the operator’s instrument for the so1 automation platform. SOL 1 is the first day on a new world; the product premise is that every team gets day one orchestration over their repos, workflows, and long-running jobs from the moment they open the panel.

The pitch

A control plane that behaves like Apollo telemetry, not like a SaaS dashboard. One surface to see system state in under three seconds, take the next correct action in under ten, and never leave the screen to know whether it worked.

Who it’s for

The engineer who already has a terminal open and wants the dashboard to earn its place next to it, not replace it.

Proof points

• Five operator surfaces in one console: Catalog (GitHub repo inventory), Workflows (n8n run history), Jobs (long-running execution), Agents (FORGE, TOMMY, ZOID, ROVER, PATHFINDER, ELEVATOR), MCP Registry
• Success criterion stated in PRODUCT.md: state read in under three seconds, next action in under ten
• Failure mode named explicitly: the operator opens a terminal because the dashboard is too soft to trust
• Built in Next.js 16 App Router; tablet and desktop, never mobile-first

mindmap
  root((Rover))
    Catalog
      GitHub repo inventory
      Org-wide health
    Workflows
      n8n run history
      Trigger surface
    Jobs
      Long-running execution
      Tail viewer
    Agents
      FORGE
      TOMMY
      ZOID
      PATHFINDER
    MCP Registry
      Tool discovery
      Schema explorer