Softlander Book a call
Agent-to-agent interoperability

Vendor-neutral agent architecture

Retain architectural choices when agent vendors or protocols change

A platform decision risks binding workflow logic to one vendor's conventions. The decision is how to retain architectural choices when agent vendors or protocols change. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to enterprise architects and sourcing stakeholders. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.

Book a 30 minute readiness callBrowse this capability group

The interaction contracts relationship

  1. Starting evidenceDependency maps

    Establish the basis for stable contract.

  2. Decision boundaryNecessary adapter

    Name the implementation-specific behaviour retained.

  3. Decision artefactVendor-neutral architecture proposal

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. Untested peers require their own compatibility evidence.

Decision

Frame the decision around stable contract

Questions and the evidence they need

Criterion / evidenceStable contract
Inspect dependency maps for the relevant constraint or observation.
Criterion / evidenceNecessary adapter
Inspect interface contracts for the relevant constraint or observation.
Criterion / evidenceExit exercise
Inspect data export routes for the relevant constraint or observation.
Read each criterion against the available evidence before deciding that additional work is needed.

The decision is how to retain architectural choices when agent vendors or protocols change. This is relevant to enterprise architects and sourcing stakeholders when a platform decision risks binding workflow logic to one vendor’s conventions. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.

The specific failure hypothesis is that business rules become embedded in proprietary orchestration features with no documented alternative. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.

Mechanism

Portability needs explicit vendor-specific boundaries

Relationships within interaction contracts

Source or conditionStable contract
Separate business meaning from supplier interfaces.
Crossing or choiceNecessary adapter
Name the implementation-specific behaviour retained.
Consequence or decisionExit exercise
Check replacement and evidence-export dependencies.
Compare authority and state at the receiving boundary. Each relationship needs evidence in the actual scope.

What this specialty examines

Vendor-neutral architecture should identify the decisions the enterprise wants to retain. Separate business contracts, data ownership and approval rules from vendor-specific adapters where useful. Portability has boundaries; some specialized features may remain deliberate dependencies.

The review should identify portable contracts, necessary vendor-specific adapters and realistic exit scenarios. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.

The tradeoff to make explicit

For this decision, abstraction preserves options while unnecessary abstraction adds cost and can obscure useful features. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.

Preparation

Connect the working inputs to the boundary being examined

Evidence packet for stable contract

Illustrative working format

BasisDependency maps
Match this description to the deployed or proposed boundary being examined.
ContextInterface contracts
Fix the participating revisions, task semantics, and unsupported combinations.
ObservationData export routes
Establish permitted access, provenance, and which task conditions it represents.
DependencyOperational requirements
Confirm the applicable revision and who resolves disputed interpretation.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with dependency maps, interface contracts, data export routes and operational requirements. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.

The scope also needs the integration owner, agreed expectations for a representative interaction case, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which business rules become embedded in proprietary orchestration features with no documented alternative from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.

How the work proceeds

Carry stable contract through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsDependency maps

    Agree the task meaning at the sending boundary.

  2. Examine the relationshipNecessary adapter

    Apply the scoped check to exit exercise.

  3. Retain the findingVendor-neutral architecture proposal

    Record the evidence, open dependencies, and the owner’s next decision.

Proposed sequence; resolve interpretation or access gaps before relying on the next step.

Fix the interaction contract and versions

Assemble dependency maps, interface contracts, data export routes and operational requirements with enterprise architects and sourcing stakeholders. Identify the participating implementations, interface revisions, authority assumptions and intended business result. Prepare messages and task-state examples from both sides, including an interrupted exchange and a disputed or incomplete outcome. The preparation output is a paired contract fixture showing what each participant expects and which differences would prevent the workflow from completing correctly.

Run and compare both sides of the exchange

Evaluate a realistic replacement scenario rather than claiming abstraction alone guarantees exit. Inspect exportable evidence, configuration, identity and operating procedures. Document which components would need rebuilding and which contracts remain stable.

Choose the contract or integration change

Summarise the comparison in a vendor-neutral architecture proposal with portability boundaries and migration dependencies. Classify each mismatch as interface validation, business meaning, identity, task state or operating behaviour. Decide whether to change a participant, add an explicit adapter rule, narrow supported combinations or defer the connection. Validate the affected pair again and preserve limitations that translation cannot resolve, especially around cancellation, authority and partial completion.

Indicative artefact

Make the vendor-neutral architecture proposal usable by its owner

Vendor-neutral architecture proposal

Illustrative working format

Annotated fieldVendor-neutral architecture proposal
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldPortability boundaries
Link supporting and contrary observations to inspectable evidence.
Annotated fieldMigration dependencies
Name the missing evidence, responsible owner, and condition for revisiting the decision.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a vendor-neutral architecture proposal with portability boundaries and migration dependencies. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.

Illustrative scenario

Examine exit exercise through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationStable contract

    Replacing a provider exposes an undocumented dependency in the task-state model.

  2. Question to examineNecessary adapter

    Exercise a replacement provider against the business task contract.

  3. Conditional next actionExit exercise

    Document the adapter dependency and portability limit exposed by the change.

Fictional example. No executed test, customer engagement, or measured outcome is implied.

Consider a fictional situation: an enterprise wants to replace an agent provider but discovers approval logic exists only inside that provider’s workflow designer. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For proprietary approval logic, consider whether the authoritative rule can live in an enterprise-controlled service. The vendor may still orchestrate work around it. That choice preserves an important decision boundary without requiring every feature to be vendor-independent.

Scope and next action

Keep the conclusion within named implementations and revisions

Confirm fit before the next commitment

Included boundaryStable contract
This review is limited to named implementations and revisions.
PrerequisiteDependency maps
The relevant owner must confirm access and the intended operating conditions.
Claim limitVendor-neutral architecture proposal
Untested peers require their own compatibility evidence.
Bring the triggering change and existing evidence; resolve the dependency that could alter the decision.

Compatibility is assessed for named implementations, versions, features and workflows. It does not establish universal conformance, vendor endorsement or interoperability with untested peers. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which a platform decision risks binding workflow logic to one vendor’s conventions; confirm which missing observation would change the owner’s next action.

Ways to engage

Related engagement scopes

AI Agent Protocol Interoperability Lab

Find where connected agents disagree. Exercise message contracts, identity propagation and failure recovery across your selected integrations.

Read about this offer

Continue exploring

Related insights and resources

Evaluation & assurance6 MIN READ

How to design a joint AI evaluation lab

A joint lab should be a governed way to create decision evidence across organisations, with shared methods but explicit ownership of systems, data and conclusions.

Agent security6 MIN READ

Agent protocols are creating a new control surface

Protocols make tools and agents interoperable, but they also standardise discovery, delegation and context exchange. Those interfaces need explicit trust and policy controls.

Agent security6 MIN READ

A practical security review for an MCP server

Review an MCP server as a privileged protocol adapter: verify tool semantics, OAuth boundaries, token audience, downstream delegation, input handling, isolation, logging and consent.

A little more clarity

Questions to consider.

Start with the questions that shape a better decision.

Does vendor neutrality mean avoiding every vendor-specific feature?

No. Use vendor-specific features deliberately where their value justifies the dependency. Preserve important contracts and exit options, and document what would require rebuilding rather than claiming universal portability.

Which dependencies constrain vendor replacement?

Start with dependency maps, interface contracts, data export routes and operational requirements. Record their revision, owner and relationship to the intended workflow. Missing context should be identified before interpreting outcomes; a sanitised fixture is useful only when its relevant differences from the operating case are understood.

How should a realistic exit scenario be assessed?

Identify portable contracts, necessary vendor-specific adapters and realistic exit scenarios. Compare both participants' accepted inputs, task states and results under a named interface revision. Include interrupted or delayed interactions. Parser acceptance should not be treated as agreement about business meaning, authority or completion.

What belongs in a vendor-neutral architecture proposal?

The proposed output is a vendor-neutral architecture proposal with portability boundaries and migration dependencies. Include the selected conditions, supporting observations, unresolved differences and next decision. A reviewer should be able to follow each important conclusion back to its evidence and understand the limits without depending on an undocumented explanation from the author.

When is a vendor-specific feature an acceptable dependency?

A vendor-specific dependency is acceptable when its value and operating fit justify the documented cost of change or exit. Retain ownership of the important decisions and avoid claiming portability where rebuilding would be required.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from enterprise architects and sourcing stakeholders may already be sufficient. In that case, capture the decision, unresolved limitations and the change that would require another review. Additional assessment should address a real gap.

What would make the findings inconclusive?

Missing dependency maps, interface contracts, data export routes and operational requirements can prevent a reliable interpretation, depending on the case. Record the specific missing observation and its implication. The owner can supply evidence, narrow the claim or defer the dependent decision; an incomplete case should not silently be counted as a pass.

Start with the decision you need to make.

Tell us about the agent workflow you want reviewed, and where you need greater clarity. Scope and availability are confirmed together.

Book a 30 minute readiness call Get the agent release checklist

Connected disciplines

Agent interoperability assessment

Decide whether agents can exchange work without losing meaning or control. The review connects interaction diagrams, message contracts, identity mappings and task-state definitions to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.

MCP architecture and security

Design an MCP integration around explicit resource and authority boundaries. The review connects client and server configurations, tool inventories, identity flows and data paths to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.

Agent2Agent protocol evaluation

Evaluate a chosen Agent2Agent implementation against workflow expectations. The review connects selected specification revision, implementation documentation, task states and authentication settings to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.