reference Updated 2026-10-06

Dashboard Metrics

What each number on the dashboard means — and what to do about it.

Attack Coverage

Which mapped components have playbook attack coverage. Every component in your library is classified by how many playbooks cover it:

  • Mature — well covered; if this component appears on an asset, the engine has plenty to say.
  • Developing — partially covered; a thin spot worth growing.
  • Gap — zero playbook coverage; the library knows the component but not what to do with it.

The Mature and Developing thresholds are adjustable in Workspace Settings → Dashboard — tune them to how you want the library judged.

Blind Spots

Mapped asset components that still have zero playbook coverage. Attack Coverage looks at the library; Blind Spots looks at your live assets: components you have already observed on real targets that no playbook can act on yet. Hover an asset to inspect which components are uncovered.

A blind spot is the most actionable metric on the page: you already did the recon, the context exists, and the only missing piece is a playbook.

Playbook Coverage Rate

The percentage of suggested playbooks that have been attempted — marked with success, failure, or not-applicable. Per asset, with navigation between assets.

A low rate means suggestions are piling up unexamined: surface area you have mapped but not tested. It is not a score to maximize — testing everything is not the goal — but a low rate with high-priority assets is a signal.

Knowledge Velocity

How quickly the workspace is gaining new knowledge — notes, links, checklist objectives, and notespaces created over the last 30 days. Useful as a personal rhythm check: mapping compounds, and this measures how often you are adding to the pile.

The top five most-used components per type, ranked by how many assets they are mapped to. It is a quick read on what your engagements actually consist of — and a hint about which components most deserve great playbook coverage.