LINC evaluation: exchanging messages across authorised systems

A fictional analysis team needs to exchange an approved infrastructure assessment with a separate coordination system. This proposed LINC demonstration uses synthetic records and test identities. It illustrates an evaluation approach rather than reporting a customer result.

Define the exchange before connecting it

The first task is to name the source, destination, message type and permitted purpose. The source retains the assessment and its approval record. The receiving system needs an authorised update containing only the agreed information. AIC and the customer define the contract and flow policy for that exchange.

LINC, Linked Intelligence Network Communications, handles exchange protocol, routing and transfer state between independently governed systems. The demonstration should preserve those responsibilities. The source application owns its information and release decision; the destination owns its acceptance of the incoming message.

Follow one message through the route

Create a versioned message carrying the agreed handling, provenance reference and content hash. Inspect the record of durable acceptance before allowing the sender to treat the message as accepted. Then follow the routing and policy decisions through to the receiving system.

The policy example should check the identity, purpose, recipient, handling and other restrictions agreed for the test. LINC uses MARKER for classification-aware flow policy. Include a message whose authority is missing and inspect the hold decision. The demonstration uses invented labels and approved test material, so the discussion can examine the mechanism without moving protected operational information.

Where the scenario includes a boundary gateway, inspect the export and import decisions separately. The source authorises the named artefact and flow. The destination validates the incoming material and acknowledges durable storage. The acceptance record should make clear when each step happened and what evidence supports the final delivered state.

Interrupt the connection and change the conditions

Pause an authorised test connection after the message has been stored. While it is unavailable, change one relevant policy condition, such as the test recipient’s permission. Reconnect and inspect whether current authority and peer identity are checked before forwarding resumes.

A second run can exercise retries and duplicate delivery. LINC describes at-least-once delivery with idempotency to prevent duplicate business effects. Agree which destination action counts as the business effect, then check its record after the retry. Also inspect the handling of a message that cannot be processed within the agreed retry policy.

These tests make recovery part of the evaluation. A successful demonstration should explain held work, rejected messages and incomplete transfers as clearly as normal delivery. The LINC security model sets out the relevant decision boundaries.

Test release responsibility explicitly

Use a synthetic source report containing information intended for different audiences. Prepare a separate derivative for the receiving system and bind approval to that derivative’s exact content. Check that the source retains protected lineage and that the destination receives only the approved reference and content.

Any real cross-domain use requires independently approved gateways, policies and accreditation for each named flow. A product demonstration supplies evidence for evaluation; the deployment owner must still establish those approvals. The test plan should record the intended environment and the outstanding acceptance work.

Make the integration decision on recorded evidence

Review the contracts, decision records, recovery behaviour and destination acknowledgement with the application owners. Estimate the engineering needed to connect the actual systems, establish policy, operate the exchange and maintain it as interfaces change. Compare the same scope with the organisation’s current integration approach before claiming a cost reduction.

The companion article explains governed message exchange with LINC. Explore its architecture and contact AIC with the systems and flows you want the demonstration to address.

View the LINC product page for capabilities, integration scope and the demonstration enquiry route.