NERVE is live across local, private and approved-cloud deployments. Book an evaluation
AIC Intelligence Suite / Intelligence Data Fabric
From source to searchable information.
NERVE brings approved files, messages, device packages, databases, APIs and feeds into one governed information fabric. Preserve the exact original. Transform supported content into a common model. Find it through NERVE Explorer, CORTEX and approved integrations.
Ingest
Transform
Preserve
Search
The information fabric
Architecture
Source families
Files
Messages
Device packages
Databases
APIs
Feeds
NERVE
Intelligence Data Fabric
Original
Exact accepted bytes and acquisition context
Canonical
Common envelope with typed content and extensions
Derived
Indexes, extractions and versioned transformation runs
Policy evaluated before results
NERVE Explorer
Governed search with exact locators
CORTEX
Owns the intelligence lifecycle
How the fabric fits together. Preservation is committed before extraction, even though the shorthand reads ingest, transform, preserve, search.
The problem
Useful information is scattered across incompatible sources.
Messages, documents, application exports and operational feeds arrive with different structures, access methods and processing histories. That leaves teams rebuilding importers, switching tools and reconstructing provenance before analysis can begin.
NERVE solves the source-to-search infrastructure problem once: connect an approved source, preserve what was acquired and make supported information discoverable through consistent concepts.
Four actions
Ingest. Transform. Preserve. Search.
Ingest
Acquire approved source material through bounded uploads, imports and versioned connectors.
Transform
Map supported structures into typed records while keeping source-specific detail.
Preserve
Retain exact originals and the history behind every transformation.
Search
Expose authorised information with exact locators and stable evidence references.
The shorthand reads ingest, transform, preserve, search. In the pipeline preservation is committed before extraction begins, so a later parser never rewrites what an earlier citation relied on.
Preservation
Preserve the original. Improve the interpretation.
The pipeline commits accepted source bytes and acquisition context before untrusted extraction begins. A better parser creates a new transformation run; it does not rewrite the original, or the output an earlier citation relied on.
Original
Accepted bytes plus acquisition context, committed once and never rewritten.
immutable
Transformation run v1
Output retained, earlier evidence reference stays attached here
Transformation run v2
New immutable output from an improved parser, nothing earlier is replaced
How a reprocessing run adds a new output while earlier citations stay resolvable.
Common model
Search the concept. Keep the source.
A message, document, transaction or location observation can share stable search semantics without losing the fields that made its source distinctive. NERVE uses a common envelope, typed content and namespaced extensions.
Meridian
3 of 6 matches shown, Meridian demonstration dataset
Message
EXAMPLE-MSG-001
“Meridian review is scheduled for Friday. Bring the archive checklist.”
Training mailbox export, message-body locator
Document
EXAMPLE-DOC-002
“Meridian archive checklist: confirm source context, preserve originals and record parser versions.”
Training document archive, page 1, paragraph 2
Generic record
EXAMPLE-ROW-003
project=Meridian; item=archive-checklist; status=review
CSV import, row 4, column project
Records from the Meridian demonstration dataset, shown here to illustrate the shared search semantics NERVE applies across every source family.
Governance
Govern access before discovery.
Search evaluates organisation, dataset, protective handling, privacy and purpose constraints before results, counts and facets are produced. Protected information never becomes visible through a search side effect.
01
A query arrives with an identity and a stated purpose
No index is consulted before the request is understood.
02
Policy is evaluated before retrieval
Five constraint families are resolved into an authorised boundary.
Organisation
Dataset
Protective handling
Privacy
Purpose
03
Only then are results, counts and facets produced
Denied material contributes nothing a user could infer from, including totals.
The AIC suite
NERVE gets information in. CORTEX turns information into intelligence.
NERVE provides source-to-search information. CORTEX provides the governed workflow for requirements, analysis, products, controlled release and feedback. Stable service contracts connect the two.
NERVE
Information infrastructure
Acquisition of approved source material
Preservation of exact originals and acquisition context
Transformation into a common model with typed content
Governed search, exact locators and evidence references
Service contracts for Explorer, CORTEX and approved integrations
CORTEX
Intelligence lifecycle
Requirements and tasking
Analysis, hypotheses and assessment
Intelligence products and reporting
Controlled release and review
Feedback into collection and tasking
Deployment
Runs in the environment your information requires.
Three deployment profiles cover different operating constraints. The logical search and evidence contracts are identical across all of them, so an evidence reference means the same thing wherever it is resolved.
Compact local node
A single constrained environment for small teams, disconnected work and field use, keeping originals and indexes local.
Deployment profile
Scale-out private deployment
On-premises infrastructure with separated workers, storage and indexes for larger volumes and stricter network boundaries.
Deployment profile
Approved cloud deployment
Managed infrastructure inside an approved tenancy, with the same logical contracts and the same evidence references as every other profile.
Deployment profile
Proof
Results trace back to the exact bytes you acquired.
NERVE is built so that any answer can be taken apart. Preservation, transformation history and policy evaluation are all inspectable, so a result stands on its evidence rather than on trust.
Independently tested
Exact-original acquisition
Accepted bytes are streamed into organisation-scoped storage under SHA-256, with immutable original metadata and audited exact-original retrieval. Scan-required content is quarantined, and ingest jobs reconcile cleanly on retry.
A hash proves byte identity. It tells you the object is unchanged, and nothing more.
Shipped
Across the platform
Transformation into a common model, derived outputs, resolvable evidence references, governance enforcement and all three deployment profiles share the same contracts, so behaviour stays consistent as holdings grow.
The pages here say exactly what the platform does, so capability is never left to implication.
Prove the chain with your sources.
Start with two or three of your own approved sources. Define the policy boundary, preserve the originals, run transformation and resolve an exact evidence reference. Agree the success measures up front.