Overview

Overview is the first page of the CORE console and the first category on its rail. It answers one question: is anything wrong, and where do I go next? It is a summary, not a second copy of every page. Each line on it links to the page that owns the subject.

This section also covers what you need before you use any other category: how to sign in, how the rail is organised, how the platform is built, and how to read what the console shows you.

Getting started

Console map

Every rail page, its ?tab= link name, and what it reads.

Architecture

Modules, operators, ClientInstance, the security spine, and where the console keeps its data.

Status and provenance

How to read a verdict, an absent value, and a derived figure.

HTTP route reference

Every route the console registers, and how each class of route is authorised.

Troubleshooting

Sign-in failures and console errors, quoted from the code.

What the Overview page shows

From top to bottom (flutter/lib/features/dashboard/views/dashboard_view.dart):

Section	What it reads	Refresh
Header pill `{healthy}/{total} healthy`	`GET /api/dashboard`: the Deployments and DaemonSets in the tracked namespaces	every 5 s while the tab is visible
KPI strip: Client instances, Workloads, Agent runs (7d), Success rate	`/api/dashboard` and `GET /api/agent-runs`	every 5 s
Needs attention	the open findings of DataEx › Trust › Harness (`GET /api/harness`), worst first	every minute
Recent agent runs	the eight most recent runs from `/api/agent-runs`	every 5 s
Platform	one line per subsystem (workloads, instances, inference, data sources from `GET /api/connections`), each a link to the page that owns it	every minute for inference and connections
Ask CORE	the orchestration chat, `POST /chat`	when you send

The auto-refresh runs only while the Overview tab is on screen. When you return to the tab, it reloads at once instead of showing the numbers you left.

What the Overview page does not show

The Overview used to repeat ten sections from other pages. They now live only on their own pages:

the workload table is on DevEx › Cluster › Namespaces;
the instance table is on DevEx › Cluster › Instances, which is the only instance table;
the inference tiers and the model router status are on DataEx › Inference;
the agent roster is on DataEx › Agents, and the schedules are on DevEx › Agent runs › Runs;
the FinOps estimate is on Intelligence › CFO Cockpit;
the data platforms are on Intelligence › Sources.