Integration scope, stated clearly.
Architects, developers and information owners need to agree an interface, a supported version and an authority boundary. A portfolio relationship does not prove technical compatibility.
Source and evidence interfaces
NERVE exposes documented search and evidence interfaces for CORTEX and approved integrations. Confirm the accepted source formats, evidence locator contract, identity delegation and denied-access behaviour. Test preservation of citations when a source is processed again.
Geospatial exchange
GTK’s official product description names enterprise and geospatial integration surfaces. Compatibility depends on the selected release, data format and target platform. Establish the export and receiving contracts, metadata mapping and handling policy with a representative exchange.
Palantir Foundry and AIP application access
PAL.NET supports a defined platform surface and the customer’s Ontology. Ask for the API Compatibility Manifest and required platform permissions. SDK entitlement and offline package distribution are separate from the platform’s own network and licensing prerequisites.
04 / PULSE
Scheduled assessment delivery
PULSE’s intended application, email and structured endpoint channels must be scoped by recipient, edition identity, marking, revision handling and the record of successful delivery. A sent notification does not demonstrate that the recipient has received the complete assessment.
For a PULSE to LINC integration, name the edition contract, destination owner and access policy. Retain the distinction between an assessed product, its delivery record and any later correction.
05 / LINC
Governed message exchange
LINC’s intended messaging layer adds durable acceptance, explicit transfer state, bounded retries and policy re-checks after disconnection. Evaluate unavailable policy, revoked access, duplicate messages and a destination that cannot acknowledge durable receipt.
A cross-domain flow also requires independent export and import decisions through the approved boundary gateway.
Cross-domain use depends on independently approved gateways, policies and accreditation for each named flow.
Exchange requirements to bring
Identify source and destination owners, versions, formats, authentication, data volume, update pattern, error handling and support responsibilities. Can the target consume the output? How is partial failure recovered? What happens to audit and provenance across the boundary? Use approved sample data to demonstrate the contract.