Dashboard

The Dashboard is the org-level home after Cloud has data. It answers “what needs attention right now?” and points you to the right work surface.

It is different from a Target’s Overview tab. The Dashboard rolls up recent activity across the org. A Target page is where you inspect one system under test in detail.

Fresh Org Checklist

When the org has no uploaded runs yet, the home page shows the setup loop:

Create a glb_ token in Tokens.
Run glubean sync from the repo to populate Specifications.
Run glubean run --upload or glubean load ... --upload to send evidence to a Target.

What it helps you answer

what failed most recently across the org
which Target needs attention
whether active alerts are firing
where the latest run evidence lives
which surface to open next: Target, Specifications, APIs, Explore, or Reports

Home View

Once runs exist, the home dashboard shows:

Pass Rate over recent functional runs
Active Alerts that have fired and need review
Recent Runs across projects and targets
shortcuts into core modules such as APIs, Specifications, Explore, and Targets

Clicking a run opens its Target run detail. Clicking an alert opens the Target’s Alerts tab.

Target Views

Most day-to-day debugging happens inside a Target:

Runs for uploaded execution records
Tests for test and contract-case history
Endpoints for endpoint-level behavior derived from traces and contracts
Performance for uploaded load runs
Metrics for custom functional metrics
Alerts for target-local alert policies and fired alerts
Settings for target identity, upload config, and baselines

Run detail is where you inspect assertions, logs, traces, screenshots, load artifacts, failure samples, and comparisons against baselines.

What Cloud Does Not Do Here

Cloud does not run your repo code from the Dashboard. Local machines and CI execute the tests; Cloud receives synced projections and uploaded evidence.

Public sharing happens through Portals, not by making a project dashboard public.