Inventory Deep Dive
Refined entity exploration — stronger category theses, representative detail stories, dual jump-selects, and a new repo entity layer grounded in session evidence.
This run refines raw inventory into clearer category theses, item stories, and faster page-to-page comparison.
Why This Feature Exists
The feature should help a reviewer understand what matters about an inventory category before they browse raw rows. It is most useful when the user knows they need inventory, but not yet which page will answer the question fastest.
Best First Page
Start with the inventory overview, then branch into the category or representative detail that matches the review question.
Open inventory overviewDesign Specs
Pages
Inventory deep-dive overview — cycle thesis, page rhythm, entity coverage, and direct jumps into category and representative detail pages.
Sessions category page — category thesis, health signals, representative cluster, raw ledger reference, and fastest drill targets.
Session representative detail — metadata, relationship cluster, event chain, c6 evidence tables, and follow-up actions.
Agents category page — software lane framing, change signals, representative cluster, and raw ledger reference.
Agent representative detail — shared execution lane story with metadata, cluster, and event sequence.
Users category page — identity posture, stack preference, host spread, and strongest drill paths.
User representative detail — operator profile, relationship cluster, event chain, and c6 evidence tables.
MCP servers category page — shared tool-surface framing, health signals, and raw server ledger reference.
MCP server representative detail — caller demand, tool surface, operational posture, and event chain.
Models category page — spend concentration, provider boundary framing, and strongest model-lane drill paths.
Model representative detail — provider facts, user lane, work pattern, and evidence tables.
API keys category page — credential trust posture, shared-lane framing, and raw ledger reference.
API key representative detail — allowlist posture, lane sharing, event sequence, and c6 evidence tables.
Endpoints category page — trust anchors, unresolved hosts, representative cluster, and raw host ledger reference.
Endpoint representative detail — environment story, relationship cluster, event chain, and evidence tables.
Capabilities category page — effective tool surface, privilege framing, and raw capability ledger reference.
Capability representative detail — schema, session demand, privilege context, and event sequence.
Files category page — sensitive-path framing, context clustering, and raw file ledger reference.
File representative detail — sensitivity, surrounding context, event sequence, and access-history evidence.
Repos category page — new raw entity tying file evidence into service, owner, and business consequence.
Repo representative detail — service context, owner routing, sensitive file cluster, and supporting evidence.
Secondary calls category page — boundary framing, weak-fit destinations, and raw destination ledger reference.
Secondary-call representative detail — destination story, precursor context, event chain, and c6 evidence tables.