Dashboard
The view when your Pearl is live.
What the operators running your Nebbos deployment see. Fires counted, actions routed, approvals pending, workloads pooled. The at-a-glance surface, not the sales deck.
01 · Fires counted
Every hook fire on your workload, over 30 days.
The platform emits a fire on every governance decision it makes — verify-first checks, KG-route lookups, credential guards, session-shard writes. The dashboard shows the 30-day rolling count, sliced by hook. Nebbos itself runs at ~62,000 fires per month; your Pearl is measured against that same baseline.
02 · Actions routed
What the approval graph handled this week.
Every consequential action the Pearl drafted, who approved it, how fast it landed, what got kicked back. The graph is the governance; the dashboard is the graph made legible.
03 · Workloads pooled
The workloads your Pearls handled, by department.
Coverage handoffs, ticket triage, close-week actions, procurement chase-ups — whatever the Pearl is scoped to. Aggregate by department, drill down to the specific call, replay any decision against a different context.
04 · Substrate understanding
Your baseline against the Nebbos 100%.
Nebbos measures every deployment against its own substrate-understanding baseline (30-day fire count on Nebbos itself). Your Pearl reads at some percentage of that. The dashboard shows the percentage, the trend, and the gap that governs promotion to production.
See the dashboard on your workload's shape.
A 30-minute walkthrough shows the panels above populated against your industry's typical workload pattern, before the four-week deployment starts.