NERVE is live across local, private and approved-cloud deployments. Book an evaluation
Try it
A search result is only useful when you can see where it came from.
Search the synthetic dataset below, then open any result to inspect its provenance: the source it was acquired from, the acquisition run, the original bytes it was derived from, and the transformation that produced the canonical record. Each field you see on a result traces back to an original.
Ways to search
Five ways to reach the same canonical record.
Explorer queries the Search API against the canonical layer. Different questions call for different entry points, and every one of them resolves to the same objects with the same provenance behind them.
01
Full text
Free-text search across the text content of canonical objects and the derived text extracted from originals. Use it when you know roughly what was said but not where it sits.
02
Structured fields
Filter on the typed fields of the common information model: object type, source, dataset, acquisition run, schema version, handling envelope. Use it to scope a question precisely before you read anything.
03
Identifier
Look up a normalised identifier, such as an account, handle, reference number or device identifier, and see which canonical objects carry it. A matching identifier means the same identifier was observed, not that it belongs to the same person.
04
Time
Query on event or observed time, acquisition time, or transformation time. These are three different clocks, and they answer three different questions. Explorer tells you which one a result was matched on.
05
Geospatial
Search location observations by area and by time window. A location observation records that a position was reported by a source. It does not establish that a person was present.
Optional
Semantic retrieval
Where it is enabled, semantic retrieval ranks candidates by similarity so related material surfaces without an exact term match. It is a derived discovery signal only: it helps you find objects, and it never changes a canonical record, replaces an exact query, or stands as evidence on its own.
Which surface
Three surfaces, three jobs.
Explorer is one of three places people work, and the three are kept apart on purpose. Operators look after the fabric, Explorer users look at the information, and CORTEX users build intelligence from it.
Operations console
Run the fabric
For platform operators and integrators who keep acquisition and transformation healthy.
Sources and connectors
Ingest jobs and schedules
Schemas and extension namespaces
Pipeline health and failure handling
Storage, retention and policy configuration
Explorer, you are here
Find and verify information
For authorised users who need the exact record and the origin behind it.
Governed discovery within your permissions
Exact records, not summaries
Provenance inspection on every result
Data-quality checks against originals
Evidence references to cite elsewhere
CORTEX
Turn information into intelligence
For analysts and reviewers working an intelligence requirement through to a reviewed product.
Requirements and tasking
Analysis workspaces
Hypotheses and competing explanations
Intelligence products and reviewed release
Feedback against the original requirement
Explorer shows you what you are authorised to see and nothing more. Broad administrative permission does not automatically grant access to protected content. Content access is governed separately from platform administration.