The problem
Separate source integrations create separate search and compliance silos when each one handles versions, provenance, and deletion differently.
What EKOS does
A shared connector framework handles scheduled and manual sync, resumable cursors, retries, source tombstones, and health state before content enters EKOS's common ingestion pipeline.
- Scheduled and manual synchronization
- Resumable cursors with retry and health state
- Google Drive folder scoping and Workspace export
- Adapters for select regulatory sources
- Source tombstones and reviewed duplicate handling
How it works
A connector account is configured with its scope, schedule, and credentials, then reports health and synchronization state.
Scheduled, manual, and webhook-accelerated syncs advance a resumable cursor with retry and backoff, so interrupted work continues instead of restarting.
The connector only discovers changes and fetches content; parsing, classification, versioning, and analysis happen in the same pipeline as a direct upload.
Deleted or moved-out sources are tombstoned, leaving Search and Ask without erasing retained operational history.
Near-duplicate documents are flagged for human-reviewed canonicalization, so one copy serves retrieval while the records beneath it are preserved.
Business outcome
Knowledge stays current without repeated manual uploads, and each supported source converges on the same downstream controls and analysis.
Proof and human control
Connector accounts retain cursor, health, synchronization, and source provenance state, while source deletions leave retrieval without erasing retained operational history.
Example in practice
A policy in a scoped Google Drive folder changes. A preview delta sync discovers the revision, creates a new EKOS version, and sends it through the standard ingestion and impact path.
Scope today
Connector synchronization is presented as preview. Production use depends on deployment-specific source authorization, configuration, and data-handling approval.