AIC Intelligence Constellation / Ecosystem architecture
Understand the roles before connecting the systems.
Understand the product responsibilities, shared foundations and intended exchange contracts before connecting systems. The Constellation identity describes the portfolio, not a validated deployment topology.
Ecosystem responsibilities / Intended exchange architecture
CORTEX
Requirements, analysis and release
NERVE
Sources, provenance and discovery
GTK 2.0
Imagery and geospatial exploitation
PAL.NET
Typed Palantir application access
PULSE
Watches, editions and delivery
LINC
Exchange protocol, routing and transfer state. Every participating product keeps its information and decision authority. Named contracts and permission checks determine which flows can be enabled.
AIC FOUNDRY + FOUNDATION
Shared messaging primitives, identity and hosting conventions.
MARKER
Classification-aware marking and information-flow policy.
SHACE
Authenticated, protected transport for the approved route.
Responsibility schematic, not evidence of an installed integration. Confirm contracts, supported releases and deployment approvals for every named flow.
Six product responsibilities
CORTEX owns the intelligence lifecycle. NERVE preserves and discovers approved sources. GTK 2.0 supports geospatial exploitation. PAL.NET provides typed access to supported Palantir services. PULSE owns scheduled area-assessment watches and editions. LINC owns exchange protocol, routing and transfer state.
Read the relationship before assuming the connection.
NERVE to CORTEX
Documented evidence interface
Confirm approved holdings, identity delegation and exact source-reference resolution for the named releases.
GTK to an intelligence workflow
Configured contribution
Agree supported output, metadata preservation and the receiving application’s interpretation.
PAL.NET to Palantir services
Separate developer interface
Match required operations to the compatibility manifest and the customer’s platform permissions.
PULSE to assessment recipients
Intended assessment service
Agree the edition structure, analyst release, recipient rights and delivery evidence.
LINC to participating systems
Intended exchange architecture
Approve the message contract, route, current policy and durable acknowledgement for each named flow.
Supported evidence lane
Approved sources enter NERVE. Authorised discovery and evidence references can support CORTEX lifecycle workflows through documented interfaces. Confirm identity delegation, source locator resolution and release-specific compatibility. The resulting report remains subject to CORTEX review and release authority.
Configured geospatial contribution
GTK can operate independently. Its contribution to another workflow requires an agreed output format and configured interface. Demonstrate metadata preservation, import policy and the receiving system’s interpretation. The illustrative disconnected route assessment is not evidence of a named customer deployment.
Separate developer integration lane
Customer .NET applications use PAL.NET to access supported Palantir services and the customer’s Ontology. This lane has its own licences, authentication and platform prerequisites. It is not the fourth stage of a NERVE, CORTEX and GTK processing pipeline.
05 / PULSE
PULSE owns the recurring assessment requirement
A PULSE watch defines an area, its intelligence questions and a cadence. The resulting edition retains its own date, cut-off, judgements, sources and review context. PULSE is the scheduled assessment service; CORTEX is the broader intelligence lifecycle workspace.
Exchange of editions through LINC is part of the intended architecture and requires an approved message contract and receiving capability. Do not infer an implemented interface from a portfolio diagram.
06 / LINC
LINC owns the exchange, not the underlying decision
The communications layer carries versioned, immutable messages and retains routing and transfer state. Product ownership, assessment judgement, information-release authority and the receiving application’s business rules remain with their respective owners.
Shared foundations support that division: AIC FOUNDRY and FOUNDATION provide messaging primitives, identity and hosting conventions; MARKER provides marking and flow policy; SHACE protects the authenticated route.
Architecture review inputs
Bring a high-level system boundary, source families, identity provider, intended interfaces and handling requirements. Which system retains the original? Where is access checked? How does a citation resolve after an update? Who authorises export and release? Record tenancy and operating-boundary assumptions explicitly.
Define the contract at every connection
For each proposed connection, record the source system, destination, exchanged objects, stable identifiers and source locators. Agree authentication, policy and marking interpretation, failure handling and the operating environment.
Name the owner of each contract. Distinguish an available documented interface from a planned or configured exchange. Keep the relevant product releases and dependencies with the design.
Select products around the work
Select NERVE for governed sources, CORTEX for intelligence workflows, GTK 2.0 for geospatial exploitation and PAL.NET for supported Palantir application access. Evaluate PULSE for scheduled area-assessment editions and LINC for durable, policy-governed exchange. Confirm availability and dependencies for the named release.
Start with the operational requirement and select the capabilities needed to answer it. A portfolio diagram is a guide to responsibilities; verify each proposed end-to-end exchange against the relevant releases.