The Heron Dashboard page had

The Heron Dashboard page had to make an agent's work legible after the fact, which is a different job to explaining what the agent does.

The hierarchy leads on time saved rather than activity volume. Heron's positioning rests on hours lost to repetitive modelling, so the product reports back in the same unit, supported by model health, active and pending item counts, and a feed of agent actions. The second half of the page covers contextual code questions, answered against a specific layout and occupancy rather than quoted in isolation.

Mobile treated density as the core problem. The four headline figures are kept grouped so the summary survives a portrait screen, and tabular content is restructured into stacked cards rather than compressed into scrollable tables.