NERVE is live across local, private and approved-cloud deployments. Book an evaluation
Resources
Understand the contract behind the platform.
Read the technical notes, clarify the terminology, and inspect the boundary of the evidence. Everything here describes how NERVE behaves in a running deployment.
Technical notes
Six notes that explain the behaviour.
Each note sets out what NERVE does, what the mechanism guarantees and where the guarantee stops. Filter by topic, or read them in order.
Preservation
6 min
Preservation and provenance
How NERVE retains originals byte-for-byte, records how each item was acquired, and keeps a readable account of every transformation that produced derived content.
Read the note
Information model
5 min
Common information model
Canonical objects share one handling envelope and carry a typed content body, so unrelated sources become comparable without losing the detail that makes each one specific.
Read the note
Search and evidence
6 min
Search and evidence
Canonical and derived content is published to the search layer in a controlled state, and every result resolves back to an exact locator inside the original item.
Read the note
Governance
5 min
Governance and authority
Handling markings, privacy profiles and purpose of use are modelled as distinct concerns, so authority to administer the platform is not the same as authority to read protected content.
Read the note
Deployment
5 min
Deployment and recovery
NERVE runs inside the organisation’s own environment, keeps processing work resumable, and can be restored from retained originals and recorded transformation parameters.
Read the note
Integration
5 min
CORTEX service boundary
CORTEX consumes NERVE through the Search API under a workload identity. The boundary is explicit, versioned and independently replaceable on either side.
Read the note
Also here
Questions, terminology and a working demonstration.
If you are checking a specific claim, start with the questions. If you are checking a word, start with the glossary. If you want to see retrieval and provenance side by side, open the Explorer.
Frequently asked questions
Direct answers on scope, connectors, offline operation, hashes, identity, retention and capacity.
Glossary
Twenty-two terms used precisely across the platform, from acquisition to workload identity.
Explorer
An illustrative discovery interface over a synthetic corpus, with provenance and exact locators on every record.
Use cases
Nine applied workflows, each naming its input, what is retained, what is derived and how it is governed.
Next
Check the claims, then test them on your own material.
Bring an approved sample and the sources you need to reach. An evaluation runs against the measures listed on the relevant use case.