Description
Knowledge Corpus Analytics lets DOTS staff inspect the scale and quality signals of the platform’s knowledge corpus across all tenants. The dashboard reports total DOTs, DIIICE-type distribution, classification, embedding, and verification coverage, Memory Bank graduations, reinforcement events, and active edge provenance methods. These are content-shape aggregates rather than a browser for individual customer knowledge.
The platform service computes the metrics from row and edge metadata on the sanctioned cross-tenant owner connection. The console renders KPIs, distribution bars, coverage indicators, and provenance breakdowns with ready, loading, empty, error, and denied states. Sparse categorical data is normalized against the fixed roster so an absent DIIICE type or edge method is represented as zero rather than disappearing from the visual comparison.
Selling Points
- Shows whether the knowledge corpus is merely growing or also becoming classified, embedded, verified, and reinforced.
- Makes DIIICE balance visible across the fleet, helping product staff detect systematic content-shape gaps.
- Tracks memory graduation and reinforcement as distinct signals instead of collapsing them into one maturity number.
- Exposes edge provenance distribution, clarifying how knowledge relationships are being established.
- Maintains the customer-content firewall by returning aggregate coverage and counts rather than row bodies.
User Story
A product operator opens the Corpus dashboard before a knowledge-quality review. They compare DOT growth with classification and embedding coverage, notice one DIIICE category is underrepresented, and verify whether Memory Bank graduations are accompanied by reinforcement activity. They also inspect which edge methods dominate. The operator walks away with measurable corpus-health questions without viewing any customer document.
Extension Surface
This capability is automatable. The corpus summary is served by packages/api/src/routes/platform.ts and consumed through apps/admin/src/lib/hooks/use-corpus-metrics.ts, allowing internal tools to retrieve the same aggregates. Metric definitions in packages/platform/src/internal/service.ts and the page composition in apps/admin/src/modules/corpus/components/CorpusPage.tsx are fixed rather than user-configurable.
Capabilities & Limits
- Reports DOT totals, DIIICE distribution, enrichment coverage, graduations, reinforcement, and edge methods.
- Zero-fills known categorical rosters for stable visual comparison.
- Keeps the cross-tenant result aggregate-only and permission-gated.
- Does not expose individual rows, documents, or customer content.
- Interactive graph structure and company-level drill-down belong to separate surfaces.
Implementation Map
packages/platform/src/internal/service.tspackages/api/src/routes/platform.tsapps/admin/src/lib/hooks/use-corpus-metrics.tsapps/admin/src/modules/corpus/components/CorpusPage.tsx