# StatusDot (/docs/charts/status-dot)

StatusDot answers "what state is this thing in right now?". Every state pairs a distinct silhouette with a semantic
color — filled circle, triangle, diamond, hollow ring, half-filled circle — so two states can never collapse into the
same mark for the 1-in-12 colorblind readers a colored disc fails.

```tsx
<span className="text-lg">
  {"The API is "}
  <StatusDot status="ok" title="API" style={{ width: "0.6em", height: "0.6em" }} />
  {" operational."}
</span>
```

## Install

```tsx
import { StatusDot } from "@microcharts/react/status-dot";

<StatusDot status="ok" title="API" />
```

Setup (package + stylesheet): [Quickstart](/docs/quickstart#set-up-with-an-ai-agent) or paste [`/agent-setup.md`](/agent-setup.md) into your agent.


## When to use it

- **Good for** — service lists, inline state in a sentence, monitoring rows.
- **Avoid for** — quantities, trends, or vocabularies past ~6 states (marks stop being memorable).

## The state contract

| status  | glyph              | token           |
| ------- | ------------------ | --------------- |
| `ok`    | filled circle      | `--mc-positive` |
| `warn`  | triangle           | `--mc-cat-1`    |
| `error` | diamond            | `--mc-negative` |
| `off`   | hollow ring        | `--mc-neutral`  |
| `busy`  | half-filled circle | `--mc-accent`   |

The pairing is a contract: `color` recolors a state but never reshapes it, and a theme must never let two states share a
silhouette.


## Variants

```tsx
// "this state is live" — monitoring contexts; gated on reduced motion
<StatusDot status="ok" pulse />
```

```tsx
<StatusDot
  status="degraded"
  states={{ degraded: { glyph: "triangle", token: "--mc-cat-1", label: "degraded" } }}
/>
```

## Edge cases

```tsx
// no "degraded" entry in the built-in map, and none supplied via `states`
<StatusDot status="degraded" />
```


## Why this default

Shape+color pairing beats a colored disc: the five silhouettes stay distinct in grayscale, print, and forced-colors,
where color-only status dots all become the same gray circle. An unknown status key renders the `off` ring with a dev
warning — never a plausible-looking wrong state.

## Accessibility

The accessible name is the state's label — **"Status: ok."** — composed with your `title` ("API. Status: ok."). The
interactive entry announces state changes through a polite live region and stays quiet on mount. `pulse` is a CSS halo
that disappears entirely under `prefers-reduced-motion`.

This chart is a single unit, so there is nothing to rove between: a click, tap, `Enter` or `Space` selects it
and fires `onSelect`, and no selection stays pinned. That is the scalar half of the shared
[interaction contract](/docs/accessibility#one-interaction-contract).

## Props

| Prop | Type | Description |
| --- | --- | --- |
| `status` (required) | `string` | Built-in ok \| warn \| error \| off \| busy, or a key of states. |
| `pulse` | `boolean` | Live-now halo (reduced-motion-gated). |
| `states` | `Record<string, { glyph; token; label }>` | Extend the vocabulary; the shape+color pairing is preserved. |
| `color` | `string` | Recolors the active state; never reshapes it. |
| `animate` | `boolean` | (interactive) Opt-in entrance motion when the chart mounts client-side — add `import "@microcharts/react/motion"` once. Inert on the server, on hydrated server HTML, and under `prefers-reduced-motion`. |

Plus the shared grammar — `data`, `domain`, `color`, `title`, `summary`, `format` — and the layout props (`width`, `height`, `className`, `style`) that every chart accepts. Interactive entries also share `animate` and `live`, and — wherever a chart has more than one navigable unit — `onActive`, `onSelect`, `selectedIndex` and `defaultSelectedIndex`; and — wherever the chart shows a hover value — `readout`. See [the shared grammar](/docs/quickstart#the-shared-grammar).