Plan intelligence workflows for constrained networks.
Deployable teams and security architects need to decide what must work locally, how material crosses a boundary and which dependencies cannot be removed.
Offline means a connection is currently unavailable. A disconnected profile is designed for a defined period or environment without that dependency. An air-gapped environment has a separately controlled physical or logical separation. None of these descriptions is an accreditation.
Establish the resident dependencies
List source material, processing services, models, indexes, identities, licences and audit storage that must be available locally. Specify the longest expected disconnection and what must happen if credentials expire, storage fills or an update is overdue.
Assess each product independently
CORTEX, NERVE and GTK have independently described local or disconnected profiles. Confirm the delivered profile for each proposed workflow. PAL.NET licensed offline bundles concern SDK distribution; access to Foundry and AIP still depends on the customer’s platform and network.
Evaluate boundary crossings
Agree source import, synchronisation, export review and conflict handling with the technical authority. Test approved material on target hardware with the network removed, then record recovery and audit behaviour. Which dependency stops the workflow? Who authorises an export? What evidence supports the assurance decision?
Evaluate LINC store-and-forward behaviour
LINC’s intended disconnected-node profile retains authorised messages durably while an approved route is unavailable. When the link returns, the sender re-checks peer identity and current policy before forwarding. A returning connection never revives expired permission.
Test interrupted acknowledgement, bounded retries, revoked recipients, duplicate delivery and an unavailable policy decision. Keep these exchange behaviours distinct from GTK’s configured local geospatial processing and from the availability of any other product’s interface.