Skip to main content

11. Integration Strategy

This section defines how the architecture integrates with existing and future systems while minimising risk, cost, and coupling. Integration is treated as a progressive capability, not a prerequisite for delivery.

11.1 Integration Principles​

Integration within this architecture is guided by the following principles:

  • Contain complexity at the edges
  • Prefer outcome exposure over system coupling
  • Deterministic first, semantic where necessary
  • Integrate late, not early
  • Never block delivery on integration completeness

These principles prioritise velocity while acknowledging long-lived legacy constraints.

11.2 Deterministic Integration Patterns​

Deterministic integration patterns are the default.

Patterns include:

  • API façade over legacy systems
  • Data access services with strict contracts
  • Event consumption with schema enforcement

Characteristics:

  • Predictable behaviour
  • Explicit error handling
  • Testable and observable

These patterns are used wherever stable interfaces exist or can be created with reasonable effort.

11.3 Semantic Integration Patterns​

Semantic integration patterns are used when deterministic integration is impractical or incomplete.

Patterns include:

  • Document-based extraction
  • AI-assisted interpretation of legacy outputs
  • Schema mapping and normalisation

Constraints:

  • Explicit confidence thresholds
  • Mandatory provenance
  • Clear degradation paths

Semantic integration is a bridge, not a permanent substitute for deterministic interfaces.

11.4 Legacy System Containment​

Legacy systems are treated as contained execution environments.

Containment strategies:

  • No direct access from the DXP
  • Minimal surface area exposure
  • Capability-based adapters isolate change

Legacy systems:

  • Remain authoritative for their data
  • Are shielded from frequent change
  • Are progressively decoupled, not replaced wholesale

This reduces blast radius and integration fragility.

11.5 Deferred Integration​

The architecture supports deferred integration.

Deferred integration:

  • Allows delivery before full system connectivity
  • Uses placeholders, stubs, or document-based inputs
  • Enables manual or AI-assisted execution initially

Deferred integration is explicit and governed, ensuring it does not become permanent by accident.