NERVE is live across local, private and approved-cloud deployments. Book an evaluation
Audience
Platform and information governance teams onboarding a live business system.
Source families
Enterprise repositories, Documents and office content, Messages and email
The workflow
01
Input
Sam defines the endpoint, the account NERVE will use and the scope it is permitted to read. The connector profile is versioned, so the exact behaviour of each run is recorded.
02
Acquisition and preservation
Incremental polls retain their acquisition windows, the source’s own identifiers and the change tokens returned by the repository. Each run is a durable acquisition in its own right, not an overwrite of the last one.
03
Transformation
Approved messages, documents and structured rows are normalised into canonical records. Repository-specific fields stay available under namespaced extensions.
04
Discovery and retrieval
The repository becomes searchable alongside archives and feeds in the same corpus, with the same query fields and the same citation behaviour.
05
Governance
The configured scope is the boundary. Material outside it is not acquired, and broad administrative permission in the source system does not automatically grant NERVE access to protected content.
When it goes wrong
Failure variant
Access is revoked mid-run, or the repository throttles. The failure is explicit rather than silent, and the checkpoint cannot advance past material that was never committed, so a restart resumes without a gap.
What this does not claim
Connector behaviour is defined by the versioned profile in use. Changing a profile starts a new acquisition lineage rather than altering the history of previous runs.
Evaluation measures
Scope enforcement against out-of-scope material
Incremental fidelity across consecutive runs
Restart behaviour after revocation or throttling
Change-token correctness
Canonical mapping coverage for repository types