The problem
Searching an entire enterprise estate creates noise, while inconsistent labels make it difficult to find the right policy set, framework, business unit, or topic.
What EKOS does
Administrators create tenant-wide, organization-scoped, or subscribable reference corpora, define controlled tags, and apply exact metadata that can be filtered without reprocessing content.
- Tenant-wide and organization-scoped corpora
- Subscribable reference collections
- Controlled tag definitions
- Manual and AI-assisted tag application
- Exact metadata facets without re-embedding
How it works
Administrators create corpora that are tenant-wide, scoped to one organization, or published as reference collections each tenant explicitly subscribes to.
Every document inherits the visibility of its corpus, and that boundary applies across document lists, Search, Ask, similarity discovery, and MCP tools.
A controlled tag vocabulary defines each tag with a slug and description, for people and for AI classification alike.
Users apply tags manually, and an AI tagger can choose only from the same closed list during ingestion.
Exact metadata facets such as agency, jurisdiction, or framework filter immediately and can change without reparsing or re-embedding.
Business outcome
Users can research the right knowledge domain while administrators maintain predictable collections and vocabulary across people and AI-assisted classification.
Proof and human control
The same corpus visibility and controlled-tag filters apply across document lists, Direct Search, Ask EKOS, similarity discovery, and MCP tools.
Example in practice
A tenant combines a subscribed regulatory reference corpus with private security and HR collections, then filters Ask EKOS to the relevant corpus and access-control tag.
Scope today
Corpus subscriptions control knowledge visibility, not legal applicability. Tags organize content and do not establish compliance mappings by themselves.