Skip to content
Design System
GitHub

A directed acyclic graph for lineage and pipelines, laid out in layers with no layout library: boxes with name, meta, status and link, neutral edges, the selected node's path highlighted, arrow keys along the edges, and GraphList, the same graph as text.

Graph lineage

Install
npx shadcn add @syncrobotic/graph

Also installs: @syncrobotic/cn, @syncrobotic/status-glyph, @syncrobotic/skeleton, @syncrobotic/table

Overview

A directed graph that flows one way: boxes in columns, inputs on the left (or above), neutral lines between them, and a text view with the same nodes.

When to use

  • Lineage: Dataset v3, the label sets it was built from, and the raw captures under them.
  • A training run's inputs (dataset, base model, config) and outputs (checkpoints, metrics, evaluations).
  • A mission's steps when some run in parallel and meet again.

Use something else

  • Every node has one parent: Tree, which reads as a list and opens and closes.
  • Steps in one line, one after the other: Stepper (a flow people go through) or Trace (a run that happened).
  • Events in time order: Timeline.
  • More than about 60 nodes, or a graph people edit: a dedicated library (React Flow, elkjs) with panning and zoom.

More examples

States and real uses. Each example is also a Storybook story and a visual regression test.

Training run 412

Arrow keys move along the connections: forward to outputs, back to inputs, across to the next node in the same column.

Graph training pipeline

Arrow keys move along the connections: forward to outputs, back to inputs, across to the next node in the same column.

Graph top to bottom

Build of Dataset v4

Arrow keys move along the connections: forward to outputs, back to inputs, across to the next node in the same column.

Graph node in error

No lineage recorded yet. It appears once Dataset v5 is built from a label set.

Graph empty

Loading

Graph loading

Picking and safety models, end to end

Arrow keys move along the connections: forward to outputs, back to inputs, across to the next node in the same column.

Graph large

Usage rules

  • For a node with several inputs: lineage, a training run's inputs and outputs, a mission's parallel steps. When every node has one parent, use a Tree.
  • Offer GraphList beside it (a Graph / List switch), as a chart offers its table: the same nodes as text, inputs before what they feed. On a phone the list reads without scrolling sideways.
  • Up to about 60 nodes. A bigger graph needs a dedicated layout library and panning; show a part of it (one node's lineage) instead.
  • Edges are neutral; the selected node's path is drawn in the ink colour and the rest steps back. No colours per edge or per kind of node.
  • Status is a shape and a word; only warning and danger are coloured. Steps that did not run are grey and say so ("Not run").
  • Names fit a box: about 28 characters show in full, longer ones end in an ellipsis. Put the detail in meta, one short line.

Changelog

  • 0.21.22026-11-21Compiles with noUncheckedIndexedAccess, as strict products build it; behaviour unchanged.
  • 0.21.12026-11-21The path walk is written as plain statements instead of a comma expression. No visible change.
  • 0.21.02026-11-20First release: a layered layout for up to about 60 nodes (longest-path layers, barycenter ordering, edges routed between boxes), left to right or top to bottom, scrolling inside its frame with the scroll fade; one Tab stop with arrow keys along the edges; selection highlights the upstream and downstream path; each node's name lists its inputs and outputs; GraphList shows the same graph as text.

How to upgrade