Slice three built the dashboard’s chrome to the mockups, and the first time it ran on the real machine the mockup’s assumption showed: the mockups had twenty nodes, and the machine had well over a hundred, most of them archived.
Hidden by default
Live work is the point of the board. The owner decided that archived sessions start hidden, with the Hide archived filter switched on from the first load and a stored preference able to turn it off for anyone who wants the whole history on screen. The counters in the header and the per-project rows count only visible nodes, so the numbers describe the picture rather than the database.
Alerts, derived not emitted
The same review found the alert code matching keywords against alert kinds that nothing in the system actually emitted. Rather than add a new source, the manager cut the collector’s alerts down to the two it genuinely knows first, a usage window resetting and the observer session stopping, and had the board derive the rest locally: the wind-down warning from the usage window, a stale source from the freshness strip, and waiting-on-you from a node’s state. Exact kind strings, stable ids, no guessing from text. The owner had asked for progress without input, so the manager made that one.