Dashboards assembled
from answers, not tickets.

Any chart in a Reactor answer pins to a dashboard with one click. A back-badge on the tile keeps the link to the answer it came from.

Describe the tile in the Add Tile dialog and the platform writes the query. Reuse a chart an earlier answer produced from the history tab.

A Raw SQL tab for the people who already know what they want. It never needs a model, so it stays available on tenants with AI switched off.

Switch a tile between a curated set of interchangeable chart types straight from its header. Authors choose which types a tile offers.

A 12-column grid with continuous height. Size tiles to their content instead of snapping to a two-column lock, and choose where each tile’s readout sits: rail, footer or drawer.

Headline numbers sit above the charts as KPI tiles and gauges, so the figure that matters is the first thing read.

Relative expressions like now-6h or now/d, resolved at request time so a rolling window keeps moving. Drag across a time axis to zoom every tile at once.

Authors pin the fields worth filtering on, auto-detected from the tiles' own axes. Scope a filter to every tile that uses the column, or exclude individual tiles.

Open a filter list and values with no data under the other active filters are struck through, so nobody picks a combination that returns nothing.

Click or drag-select on a chart to filter the rest. A count-and-share popover offers quick actions before anything is applied.

Published tiles run from an immutable source query rewritten into safe named parameters. Values are bound, never concatenated into the SQL.

Save the current filters and time range as a named view, per person and per dashboard, and return to it in one click.

A refresh patches just the tile whose data changed. The other charts on the dashboard are not redrawn.

One compact control replaces the refresh button, countdown and interval menu. Its border burns down toward the next refresh and fills as a pass runs, with a bead per tile.

If a refresh errors, the tile keeps its last good snapshot and shows the failure, instead of blanking a wall of charts.

Default interval, refresh-on-open, default time range and refresh concurrency are tenant settings. Ship sensible defaults and let each tenant tune them.

A published dashboard can refresh on a schedule as its owner, so the snapshot is fresh before anyone opens it.

Ask for a readout of any chart. The interpretation is governed like every other LLM call, and counts against the monthly AI cap of the Refinery it runs under.

Attach a rule to a tile: aggregate a column, compare to a threshold. A breach raises a deduplicated Action Item in the Inbox and can auto-start a Chain.

Grant a user or a group access to a dashboard. Sharing is a general mechanism, not a Radar special case.

Export the whole dashboard as a PDF, or any tile as CSV or Excel.

A published dashboard rejects structural edits and rolls a version number. Revert to draft to change it, publish to lock it again.

Share, refresh and alert events land in the hash-chained audit ledger like any other governed action.

Dashboards travel inside signed Reagent bundles, with their data sources bound at import time.