The problem
A file alone does not reveal where it came from, how it changed, what it connects to, or whether anyone needs to respond.
What EKOS does
A durable ingestion workflow stores the source, extracts searchable passages, classifies sensitivity, deduplicates identical content, and creates a new version when the content changes.
- Durable asynchronous ingestion with visible job state
- Parsing for common business formats and scanned PDFs
- Content-hash deduplication
- Retained and downloadable version history
- One dossier for context, relationships, impact, and alerts
How it works
An upload or connector change enters a durable background workflow with visible job state, retry, and cancel controls.
EKOS stores the source bytes first, then extracts text and structure from common business formats, with local OCR fallback for scanned PDFs.
Content is split into searchable passages, classified for sensitivity, embedded, and indexed; identical content is deduplicated by hash.
Changed content creates a new version rather than overwriting the history that citations and audit decisions depend on.
The finished dossier gathers versions, tags, metadata, relationships, impact items, and notifications around the document.
Business outcome
Teams gain one place to understand the document, its history, related knowledge, processing state, impact work, and alerts.
Proof and human control
The dossier keeps current and historical versions, source metadata, controlled tags, relationships, impact items, and notifications attached to the same governed record.
Example in practice
A policy owner uploads a revised access-control policy. EKOS creates version two, retains version one, indexes the current language, and starts impact analysis for relationships that depended on changed passages.
Scope today
Versioned ingestion is available. The complete Living Dossier application experience is offered as a preview.