# Fleet Zoom (Notchset): prompt.md (v1.0.0)

- id: `fleet-zoom` · version 1.0.0 · block · pro (Pro)
- category: Application UI
- build: Base UI (one set of files; its dependencies follow the build)
- install (this build): `npx shadcn@latest add @beautiful-ui-pro/fleet-zoom`
- npm dependencies: class-variance-authority@^0.7
- registry dependencies: utils, https://beautiful-ui.dev/r/notchset-foundation.json
- docs: https://beautiful-ui.dev/components/fleet-zoom
- The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand.

A zoomable map of a fleet: teams hold agents, agents hold runs, on a dot grid that scales with zoom; semantic zoom shows team meta, agent names and quality, and runs only once each has room; wheel zooms at the cursor, drag pans, a click flies in, keys pan and zoom, Esc goes up a level, a guided tour flies to a failed run, and the aside names the level with its numbers.

## Build it
- Stack: React 19 (`ref` is a plain prop), TypeScript, Tailwind CSS v4 utilities, a shadcn-initialised project with the `@/*` alias.
- Packages: `class-variance-authority@^0.7`.
- Files: `components/ui/notchset/blocks/fleet-zoom.tsx`; shared code: `lib/beautiful-ui/notchset/instrument.tsx`, `lib/beautiful-ui/notchset/root.ts`, `lib/beautiful-ui/notchset/button-variants.ts`.
- Registry dependencies, installed with it automatically: shadcn `utils` (cn), `notchset-foundation`.
- Builds: one set of files for both, but its dependencies come in Base UI and Radix builds. Install the one that matches the project (see Install): a free item's bare URL installs the Base UI build of it and its dependencies.
- Exports to keep: `FleetZoom`, and every exported type.
- CSS: the install adds the notchset foundation (tokens, keyframes, motion levels) to your global stylesheet once. Nothing to import by hand.
- Re-running `add` (or `--overwrite`) re-applies those rules: put overrides in your own CSS, never in the installed rules.
- Tokens: retheme with the `--notchset-*` custom properties (`--notchset-check`, `--notchset-control-edge`, `--notchset-draw-from`, `--notchset-ease-bloom`, `--notchset-ease-glide`, `--notchset-ease-key-down`, `--notchset-ease-key-up`, `--notchset-ease-travel`, `--notchset-fade`, `--notchset-focus-color`, `--notchset-focus-inset`, `--notchset-grow-to`, `--notchset-key-down`, `--notchset-key-up`, `--notchset-life-from`, `--notchset-life-ms`, `--notchset-node-blink`, `--notchset-node-bloom`, `--notchset-node-delay`, `--notchset-plate-color`, `--notchset-rise-from`, `--notchset-rule`, `--notchset-scan-to`, `--notchset-scroll`, `--notchset-signal`, `--notchset-sweep-to`, `--notchset-travel`). Never add Tailwind colour classes inside the component.

```tsx
import { FleetZoom, type FleetRun, type FleetTeam } from "@/components/ui/notchset/blocks/fleet-zoom";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `FleetZoom` | `fleet-zoom` | Breadcrumb and tour, the zoomable map with its controls, and the aside. |

Style a part with `[data-slot="<slot>"]` selectors or its `className`; keep the attributes when editing.

## Sound
- Keep every `data-slot` and `data-sound` attribute: the sound layer reads them.
- Installing this item adds no audio. Nothing plays until the app mounts `SoundProvider` once (install: `npx shadcn@latest add https://beautiful-ui.dev/r/notchset-sound.json`, import from `@/components/ui/notchset/sound-provider`); `useSound()` gives `muted` and `setMuted` for a mute control. Without a provider the audio engine never loads.

## Match the original
- Read `components/ui/notchset/blocks/fleet-zoom.tsx` as the reference implementation before changing or recreating anything, and match it: sizes, colours per theme, motion timings, copy and behaviour.
- If you deviate (a prop you can't honour, a style you changed, a dependency you swapped), say so in your reply, part by part.
- Keep the accessibility contract, the keyboard map and the motion levels listed below.

## Use it when
- zoomable map, semantic zoom, fleet overview, drill down, treemap navigation, infrastructure map, agent fleet, Notchset
- Drilling from an organisation down to one failing job on one screen
- A fleet small enough to draw: a few teams and dozens of agents

### Not when
- Thousands of nodes: use a canvas or a table with filters
- Flat lists: use a data table

## Mistakes
- Keep runs per agent to about a dozen; they are drawn as boxes
- Wheel zoom captures the wheel over the map; keep the map away from the page's main scroll path on phones

## Usage

```tsx
import { FleetZoom, type FleetRun, type FleetTeam } from "@/components/ui/notchset/blocks/fleet-zoom";

export function Fleet({ teams }: { teams: FleetTeam[] }) {
  return <FleetZoom workspace="Acme Labs" teams={teams} onOpenTrace={(run: FleetRun) => window.open(`/runs/${run.id}`)} />;
}
```

## Props

| Prop | Type | Default | What it does |
|---|---|---|---|
| `teams` | `{ id, name, agents: { id, name, quality, p95, runs: { id, name, status, duration, tokens, cost, error? }[] }[] }[]` |  | status is ok, failed or running; duration in seconds. |
| `workspace` | `string` |  | The root of the breadcrumb and the first level. |
| `threshold / onOpenTrace` | `number / (run) => void` |  | Quality below threshold reads in signal (85); OPEN TRACE → on a run. |

Full docs: https://beautiful-ui.dev/components/fleet-zoom

## Customising
- Colours: the component reads your shadcn tokens (`--background`, `--foreground`, `--border` …), refined by the `--notchset-*` tokens. The signal colour is `--notchset-signal` (it falls back to `--destructive`). Set tokens on `:root`, or on any container to retheme one area.
- Dark mode follows the `.dark` class on an ancestor (the shadcn and next-themes convention).
- Update later by re-running the install with `--overwrite` (review the diff if you edited it). Changelog: https://beautiful-ui.dev/r/changelog.json

## Keyboard

| Keys | Action |
|---|---|
| Arrows | Pan the map |
| + / − | Zoom |
| 0 | Fit the whole fleet |
| Esc | Up one level |
| Tab then Enter | Fly to a team, agent or run |

## Performance

- Only boxes in view are drawn, and runs only inside agents wide enough to show them.

## Responsive

- Under 820px (container width) the aside moves under the map.

## Motion inventory

| Interaction | What moves |
|---|---|
| Fly | Every box glides to the new camera (700ms) |
| Tour | Team → agent → failed run → fleet, 2.2s a step |
| Aside | The headline value rolls and its bar glides |

## Accessibility contract (preserve when editing)
- The map is a labelled application region that names its keys; teams and agents are buttons, runs become reachable once their agent is focused
- The breadcrumb is a nav whose last item is aria-current; the aside is a polite live region

## Install

```bash
npx shadcn@latest add @beautiful-ui-pro/fleet-zoom
```

Pro item: needs the `@beautiful-ui-pro` registry in `components.json` and `BEAUTIFUL_UI_TOKEN` in `.env.local` (https://beautiful-ui.dev/account). Setup: https://beautiful-ui.dev/docs/pro. Your components.json `style` picks the build: radix-*, new-york and default get Radix, base-* gets Base UI.

## Credits
- Built on shadcn/ui (https://ui.shadcn.com)

The notchset foundation (the tokens listed above, keyframes and motion levels) installs once with the first component; its CSS is public at https://beautiful-ui.dev/r/notchset-foundation.json.