DOSFI Academy · Transport Layer Track

The Mesh-Native Transport Layer & MeshNativeExchange

A beginner-to-intermediate track covering how DOSFI moves intelligence across the mesh — five adapters, seven lifecycle phases, bundle envelopes, DIU metering, and the MeshNativeExchange settlement flow.

University (advanced) track

Transport Layer and MeshNativeExchange modules require DOSFI Academy enrollment. Log in or register to unlock.

Course Outline

Eight modules, ordered for learners new to the Transport Layer. Begin with the introduction (free), then enroll to unlock the full track.

1

Introduction to the Mesh-Native Transport Layer

freeBeginner · 45 min

What the Transport Layer is, the bundle unit, and where it sits in the DOSFI stack.

Preview
2

The Five Transport Adapters

paidBeginner · 1h 10m

Identity, Privacy, Routing, Economics, Audit — and why their order is fixed.

Open
3

The Seven-Phase Transport Lifecycle

paidIntermediate · 1h 20m

Submit → Validate → Enrich → Route → Meter → Transit → Settle.

Open
4

Bundle Envelope Schema Basics

paidIntermediate · 1h

bundle_id, bundle_type, metadata, and how adapters read the envelope.

Open
5

DIU Metering & Spend for Transport

premiumIntermediate · 1h 15m

What DIU measures, estimate vs settled spend, and why DIU is compute-backed.

Open
6

MeshNativeExchange Settlement Flow

premiumIntermediate · 1h 10m

How a metered bundle becomes a settled transaction in Vital.

Open
7

Transport × DOSFI Foundations

paidIntermediate · 1h

The boundary between Foundations (local) and Transport (cross-device).

Open
8

Transport × MeshInfer.AI Inference Validation

premiumIntermediate · 1h 5m

How MeshInfer validates inference during transit and attaches a proof.

Open

Learning Objectives

By the end of this track you will be able to:

  • 1Describe the purpose and placement of the Transport Layer in DOSFI
  • 2Name the five transport adapters and explain why their order is fixed
  • 3Walk a bundle through the seven-phase lifecycle from Submit to Settle
  • 4Read a bundle envelope and identify which adapter consumes each field
  • 5Explain DIU metering and distinguish estimated from settled spend
  • 6Trace a transport bill through the MeshNativeExchange settlement flow
  • 7Explain how Transport builds on DOSFI Foundations without blurring boundaries
  • 8Describe how MeshInfer validates inference integrity during transit

How the pieces fit

A simplified view of where the Transport Layer lives in the DOSFI stack.

   +---------------------------+
   |    Mesh-Native App / Agent   |
   +--------------+------------+
                  |
          submit(bundle)  /  status(bundle_id)
                  v
   +---------------------------+
   |   Transport Layer (DOSFI)  |
   |  Identity -> Privacy ->    |
   |  Routing -> Economics ->   |
   |  Audit   (fixed order)     |
   +-------+-------------+------+
           |             |
           v             v
+----------------+   +-------------------+
| DOSFI          |   | MeshInfer.AI      |
| Foundations    |   | (inference +       |
| (local devices)|   |  validation proof)|
+----------------+   +---------+---------+
                               |
                               v
                    +---------------------+
                    | MeshNativeExchange   |
                    | (settle in Vital)    |
                    +---------------------+

Glossary

Transport Layer

The DOSFI subsystem that moves bundles of intelligence safely and verifiably across mesh nodes.

Bundle

The unit of transport. An envelope carrying a payload, metadata, and identity provenance, identified by a unique bundle_id.

Adapter

A deterministic stage that enforces one transport concern — Identity, Privacy, Routing, Economics, or Audit.

bundle_id

A unique, stable identifier for a bundle that makes transport idempotent on re-submission.

bundle_type

The category of work a bundle carries (e.g. inference_request, storage_sync, agent_handoff). It selects eligible executors and routing weights.

DIU

Distributed Intelligence Unit — the compute-backed unit used to measure and settle transport and inference work.

Vital

The Distributed Intelligence Unit (DIU) settlement asset used by MeshNativeExchange, with a fixed hard cap of 10,000,000,000.

MeshNativeExchange (MNE)

The authoritative settlement layer of the DOSFI ecosystem that finalizes transport spend in Vital.

Lifecycle

The seven phases every bundle passes through: Submit, Validate, Enrich, Route, Meter, Transit, Settle.

Audit entry

An append-only, hash-linked record of a bundle's journey, finalized after settlement.

Ready to build transport-aware mesh-native apps?

Enroll to unlock the full Transport Layer and MeshNativeExchange track.