This layer defines the mechanism by which data physically moves, grouped into four canonical exchange patterns, each realised as a set of Technology Services: • Machine to Machine Synchronous API Exchange: API Gateway connects to API Manager (aggregation), supported by Request Validation Service, Identity Provider, API Contract Service, and Access Management Platform - together forming the request/response API pattern with security and contract enforcement built in. • Async Reliable Messaging: Message Broker, Event Manager, Protocol Mediation Service, Enterprise Service Bus, and Message Transformation & Mapping Service - no internal relationships drawn between them, but together they represent the decoupled, guaranteed-delivery messaging pattern. • Batch Data Transfer: Data Publication Service, Batch Analytics Processing Service, Message Transformation & Mapping Service - the scheduled, bulk-transfer pattern. • Event Streaming: Event Manager, Streaming Analytics Processing Service, AI Feature Service, Message Broker - the continuous, real-time pattern. Note that Message Broker, Event Manager, and Message Transformation & Mapping Service each appear in more than one group - confirm in Archi whether these are the same reused element (fine) or duplicated instances (should be merged). In short: this layer answers "by what technical mechanism does the data actually get transmitted?" - it contains no business or semantic meaning, only the transport-level pattern.