inventory overview
Inventory should answer the security question first and the catalog question second.
This mockup treats the inventory index as a triage surface built from existing table and metric components. The goal is to route the operator into the few entity lanes that actually change trust, blast radius, or boundary posture.
Priority entity lanes
6
Immediate drill path
NaN
Shared-lane stories
3
Stable majority
NaN
Priority lanes
Entity types ranked by meaning
Significance
Entity | Operator read | Question answered | Count | Next |
|---|---|---|---|---|
Sessions | 2 sessions matter now | Which session changed the overall security picture? | 43 | Open m2 mockup |
MCP Servers | 1 server matters most | Which servers most change what agents can reach? | 6 | Open m2 mockup |
API Keys | 1 key changes the story | Which credential lane matters most right now? | 3 | Open m2 mockup |
Files | 12 file paths matter | Which files deserve attention before the full path list? | 340 | Open m2 mockup |
Repos | 3 repos matter now | Which repos make the rest of the inventory suddenly important? | 8 | Open m2 mockup |
Secondary Calls | 2 destinations matter | Which external destinations matter most right now? | 28 | Open m2 mockup |
Pressure read
How close the inventory is to being explainable
component-only
8
Trust anchors resolved
+1
1
Boundary stories explained
+1
11
Inventory grouped by meaning
2
Blind spots still active
What this version is proving
The inventory index can stay inside the existing layer while still feeling meaning-first, interactive, and action-oriented.
Best next build target :
MCP Servers
Reason :
It is the clearest cross-boundary lane and already has enough c9 meaning data plus c6 reference data to support a full mockup pass.
Fallback path :
Every priority lane now has a matching `m2` mockup route, so the overview can keep the operator inside one component-only pass.