Transport Layer Architecture: ABI Boundary & Subsystem Placement
Subsystem placement, the ABI boundary, and the deterministic execution order of the Transport Layer.
About this course
Vertical stack context: DOSFIUniversity (research) → DOSFI Academy (this course) → MeshNativeExchange (publishing & monetizing). Students progress from Learning → Building → Publishing → Monetizing. The DOSFI Mesh-Native Transport Layer is a subsystem with a precise ABI boundary and a fixed adapter execution order. This module specifies the architecture at an architect level: where the Transport subsystem sits, the contract at its ABI boundary, and the deterministic order in which adapters run for every bundle. Outputs are deterministic: given the same bundle and mesh state, transport produces the same decision. This course provides a deep dive into the DOSFI Transport Layer Architecture, focusing on the critical ABI boundary between the DIU and the Mesh-Native runtime. Participants will analyze subsystem placement, adapter contracts, and the deterministic routing policies required for high-fidelity Node communication within the MNE framework.
What you'll build
- Define the functional boundary of the DIU within the DOSFI stack
- Implement custom Transport Layer adapters using the Bundle Schema
- Configure routing policies to enforce Privacy Tier requirements
- Validate State Machine transitions across the Identity Fabric
- Execute complex telemetry orchestration via MeshInfer pipelines
Prerequisites
- Intermediate knowledge of Mesh-Native system primitives
- Familiarity with DIU lifecycle management
- Understanding of asynchronous State Machine execution