Skip to main content

​
Layout

The shell is fixed: a 260px sidebar on the left, a 59px sticky header, and a 1200px content column. No alternating sections, no hero illustrations between rows. Everything sits on the Framer dark canvas with charcoal surfaces and 1px graphite hairlines. The sidebar carries the workspace switcher, product navigation, Docs + Support links, and an operational status pill at the bottom. Workspace selection is persisted through /api/workspace/selection.

​
Sections

First viewport: workspace name, plan, plan status, recent run count. Below: the onboarding wizard (until you have one synced run), a 3-card snapshot, two quota bars, the most recent runs table.
A 2-column grid of project cards. Each card carries a folder icon, the project name, and a one-line description. Click opens the project detail view.
A flat table of every synced run. Columns: client run id (violet mono), recipe, runtime, status pill (green / yellow / red / blue), created date. Hover reveals the open-arrow on the right.
Each run has a detail page and an audit tab. The detail page reads Cloud run metadata, manifest, metrics, logs, artifacts, signatures, and compliance mapping through the browser-safe API proxy.
Pick two runs. The page shows the manifest fields side by side and a metric delta table at the bottom. Up = green, down = red, no change = muted.
Lists Cloud claims and opens claim detail pages. Claim detail links the claim, falsification state, evidence summary, and related run context when available.
The curated runtime metadata that powers worldflux init --recipe. Filter by runtime, tier, or free-text. Each card has provider, VRAM, benchmark id, endpoint types, and any known issues.
Disabled preview for future benchmark rankings. It does not expose production ranking data yet.
Disabled preview for a future counterexample catalog. It does not expose production counterexample data yet.
API keys (one-time secret panel), Workspace, Billing (Stripe checkout and portal), and Profile (privacy + DSAR). Members exists as a page, but it intentionally renders a disabled state until Cloud exposes the production member list.

​
Run detail

Open a run from the table. The detail page stacks:
  1. Header card. Eyebrow Run · <runtime>, violet mono client run id, status pill.
  2. Share. Create, open, or revoke public links for runs with verified evidence-package artifacts.
  3. Deploy metrics. Every key under manifest.metrics rendered as a small tile.
  4. Metrics chart. Line chart for numeric metric keys present in the run manifest.
  5. Logs. Virtualized scroll, line numbers, monospace.
  6. Artifacts. Left list, right viewer. JSON inline, HTML in a sandboxed iframe, video and image with signed URLs.

​
Public share

A share link is read-only and public-safe. The recipient sees the public run header, evidence summary, and allowlisted artifact metadata for a verified evidence package. They cannot revoke, edit, or follow back to the workspace. If the share owner sets a password, the link gates on a password screen first. Unavailable public-share states are explicit: not found, revoked, expired, password required, wrong password, unverified evidence, and filtered artifact. The public page renders those states without falling back to dashboard controls or private ids.

​
Status palette

The dashboard uses vivid status colors strictly for product data:
TokenHexMeaning
--ok#22c55eRun succeeded; quota healthy
--info (opened blue)#70b8ffRun in progress
--warn (complained yellow)#ffca16Quota above 80%; queued
--danger#ff5577Run failed; quota above 90%
--click#d44df0Secondary product-data accent
--brand#6a4cf5Code identity and selected metadata
These colors stay inside data rows and dots. Section backgrounds, button fills, and decorative accents do not borrow them.