NERVE is live across local, private and approved-cloud deployments. Book an evaluation
Audience
Analysts who need one answer across holdings that arrived by very different routes.
Source families
All supported families
The workflow
01
Input
Priya queries an identifier and a time range through CORTEX, which calls NERVE through the service boundary rather than reading stores directly.
02
Acquisition and preservation
Nothing is acquired at query time. The query runs against canonical and derived records that were published by earlier acquisitions.
03
Transformation
Because every family shares the common envelope, one set of query fields reaches a message from a mailbox, a call record from a device package and a row from a repository export.
04
Discovery and retrieval
NERVE validates the calling service identity plus the delegated authority of the human behind it, then returns authorised canonical and derived matches with exact evidence references.
05
Governance
Matches the searching account is not authorised to see do not contribute to counts or facets. The result set and the numbers describing it are built from the same authorised view.
When it goes wrong
Failure variant
Part of the corpus is inaccessible to this account. Those matches are excluded from counts and facets rather than being hinted at through a total that does not match the visible rows.
What this does not claim
NERVE gets information in and makes it searchable. CORTEX turns that information into intelligence. NERVE does not make the analytical judgement.
Evaluation measures
Semantic field consistency across families
Source visibility under delegated authority
Exact evidence resolution from a result
Authorised search usefulness against real questions
Query behaviour after reindexing