Embedding Map | Zyeon UI

Preview in your theme

status='ready' with a query. 136 chunks, five clusters, one question embedded into the same space. The dashed connectors follow query.neighborIds — the retriever's OWN top-5 — which is why rank 3 runs across the map to a billing chunk the projection put nowhere near the question. Hover or Tab in and walk the cloud with the arrow keys (they jump to the nearest point in that direction, not to the next node in the DOM); Enter selects, Escape clears the selection and then the cluster filter; the legend chips isolate a cluster without ever re-fitting the map.

Queryhow do I rotate an expired API key without downtime?

onSelectPoint: null · onClusterIsolate: null

The same query with NO neighborIds. The component falls back to 2-D nearest and admits it in the footnote — and the guess is visibly wrong: it never reaches the billing chunk the retriever really returned third, because the projection buried it on the far side. This is why the contract takes the ranking instead of computing one.

Queryhow do I rotate an expired API key without downtime?

Neighbours estimated from the 2-D picture — pass query.neighborIds for the retriever's real ranking.

status='ready', query={null} — the same corpus with no question in flight: no rings, no connectors, no similarity numbers. Cluster identity is carried by colour AND mark shape, so it survives greyscale and colour-blindness.

status='ready' with 3,964 chunks and maxPoints=700. The sample is a stride, not the first 700, so every cluster keeps its share — and the footnote states the real total instead of quietly drawing a thinner cloud. clusters is omitted here, so the legend falls back to the raw cluster ids, and clusters 6–7 reuse chart-1/chart-2 with a new mark shape.

Showing 700 of 3,964 points (evenly sampled across the dataset)

status='ready' with hostile data: a duplicate id, a NaN coordinate, every x identical (a zero-width extent that would divide by zero), two chunks on exactly the same spot, and a six-sentence label. Two rows are dropped and counted in the footnote; the degenerate axis is centred instead of collapsed; the long label wraps in the tooltip rather than being clipped.

2 skipped: duplicate id or missing coordinates

status='loading' — a shimmer grid in exactly the box the plot will occupy, so nothing jumps when the projection lands. The pulse stops under prefers-reduced-motion; a screen reader hears one sr-only status line.

status='empty' — the corpus has not been embedded yet. A 'ready' payload with nothing drawable falls through to this same body: a card that claims to be ready and paints an empty box is a bug you debug twice.

Nothing has been embedded yet.

status='error' — the projection job itself failed, which is a different failure from a point being odd, so it reads differently and offers a retry.

The UMAP job timed out after 60s. run-id: proj_7f2c-9ad1

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro