The surfaces
Projects
The directory of work, laid out by project kind, with digests of what changed recently.
Experiments and runs
Run detail, comparison, lineage, trajectories, steps and trials.
Charts
Curves, stat tiles, expression panels, zoom, and the captured rows behind them.
Files
Workspace files, the Shared folder, and per-entity artifact explorers.
Search
Filters and meaning over the whole record.
Assistant
Ask questions of your lab’s history, and approve any write before it lands.
Workspaces and team
Shelves, write permissions, members, devices and settings.
Integrations
GitHub, Weights & Biases and Benchling.
Things worth knowing up front
The workspace switcher scopes almost everything
The workspace switcher scopes almost everything
Projects, Files and search results are all filtered by the workspace you are in. Choose All workspaces for cross-workspace discovery — a project you cannot find is usually a project filed somewhere else.Your selection persists. A missing selection falls back to the oldest workspace.
AI summaries are generated, and dated
AI summaries are generated, and dated
Entity pages lead with a generated summary, below which sits the authored Overview — the document a person or agent wrote. The two are visually distinct so a generated paragraph is never mistaken for a teammate’s claim.Summaries refresh on a queue rather than on every read; a stale one is marked, not silently served as current.
Computed is never shown as captured
Computed is never shown as captured
Expression panels carry an ƒ chip; derived series carry a derived chip with producer and computed-at on hover. Grouping, smoothing and pivoting are never presented as source rows, and a panel’s value table is labeled computed.This is a hard rule throughout the dashboard: post-hoc numbers do not masquerade as training-loop capture.
Reads are open, writes may not be
Reads are open, writes may not be
Every member of the team reads every workspace. What a workspace can restrict is who may edit what is filed in it. See workspaces.
An empty state is not an error state
An empty state is not an error state
A failed load renders as a failure, never as “nothing here”. “No papers recorded” on a project that has papers would be a confident lie about your own data, so the two states are kept distinct everywhere they appear.