NERVE is live across local, private and approved-cloud deployments. Book an evaluation
The NERVE–CORTEX integration contract.
CORTEX consumes NERVE through the Search API under a workload identity. The boundary is explicit, versioned and independently replaceable on either side.
Integration
5 min
The division of labour
NERVE gets information in. CORTEX turns information into intelligence. NERVE owns acquisition, preservation, normalisation, derivation and governed search publication. CORTEX owns requirements, analysis, hypothesis work, intelligence products and reviewed release.
How CORTEX reads NERVE
CORTEX consumes NERVE through the Search API. It reads published canonical and derived objects, and it receives the exact locators that allow a product to cite a precise position inside an original item. It does not reach into storage directly and it does not bypass publication state.
Identity and policy at the boundary
The integration runs under a workload identity issued to CORTEX. That identity carries its own permissions and is constrained by the same handling markings and privacy profiles that apply to human users. Access can be audited and revoked without affecting other consumers.
Versioned and replaceable
The contract is versioned, so each side can evolve without breaking the other. A different analytical tool can be placed on top of NERVE, and CORTEX can be fed by a different fabric. Either product can be adopted on its own: the integration is an option rather than a prerequisite.
What the contract does not settle
An integration contract describes the interface. Support for a named third-party system still depends on the specific implementation, the versions in use and the licensing in force in the operating environment.
Key points
NERVE gets information in. CORTEX turns information into intelligence.
CORTEX reads published canonical and derived objects through the Search API.
Access is granted to a workload identity and constrained by the same handling policy as human users.
Either product can be adopted on its own. The integration is an option, not a prerequisite.
Where this stops
The integration contract is versioned. Support for a named third-party system still depends on the specific implementation, versions and licensing in the operating environment.
Related
Next
See the behaviour on your own material.
An evaluation runs NERVE against an approved sample in your environment, with the originals retained and every transformation recorded.