All coursesAdvanced Architect Curriculum

Mesh-Native Transport & MeshNativeExchange Settlement

The full technical specification of the DOSFI Mesh-Native Transport Layer and the MeshNativeExchange settlement system — adapter specifications, the seven-phase lifecycle, bundle envelope schema, DIU metering, and settlement finality. Architect-level. Deterministic. Subsystem-oriented.

Gated Access

All University modules require authenticated enrollment. Transport and MNE modules require University-level access — completion of the DOSFI Foundations tier must precede enrollment.

Course Map

Updated University Course Map

Two advanced architect-level courses inserted into the Architect track, positioned after the existing four architect courses and before the Architect Certification Exam.

Architect · ADV-1 University-level

DOSFI Mesh-Native Transport Layer

Architect-level specification of the DOSFI transport layer: ABI boundary, adapter execution order, the seven-phase lifecycle, bundle envelope schema, typed bundles, and routing-policy scoring.

12h$29915 modules

View course

Architect · ADV-2 University-level

MeshNativeExchange Settlement Protocol

Architect-level specification of the MeshNativeExchange settlement protocol: DIU metering, price scaling, two-phase issuance, settlement finality, and the transport binding to MNE.

10h$2999 modules

View course

Architect · Advanced — Transport

DOSFI Mesh-Native Transport Layer

A deterministic, subsystem-oriented treatment of the DOSFI Mesh-Native Transport Layer. Covers the ABI boundary between the runtime and the transport substrate, the five canonical adapters and their fixed execution order, the seven-phase lifecycle with explicit state transitions, the bundle envelope schema, typed bundle definitions, and routing-policy scoring across trust, geo-compliance, capacity, latency, and operator preferences.

15 modules12 hours$299 · PremiumRequires DOSFI Foundations completion + authenticated enrollment

View full course

Module Specifications

Architect · Advanced — Settlement

MeshNativeExchange Settlement Protocol

A subsystem-oriented specification of the MeshNativeExchange (MNE) settlement system that finalizes compute-backed Vital (DIU) issuance. Covers DIU metering algorithms, DIU price scaling, the settlement workflow with its state machine, two-phase issuance commit, settlement finality and append-only ledger integrity, and the MNE transport binding.

9 modules10 hours$299 · PremiumRequires DOSFI Foundations completion + authenticated enrollment

View full course

Module Specifications

Reference

Technical Glossary

Canonical definitions for every term used across the transport and settlement specification.

Term

Definition

ABI Boundary

The stable, versioned contract between the DOSFI runtime and the transport layer; the runtime may only invoke declared entry points and may not reorder adapter execution.

Adapter

A single-responsibility transport subsystem (Identity, Privacy, Routing, Economics, Audit) that reads its inputs, writes exactly one envelope field, and returns accept or reject.

Bundle Envelope

The canonical, versioned container (dosfi.transport.v1) carrying identity, privacy, route, economics, audit, payload, and signatures through the lifecycle.

Typed Bundle

The payload union (InferenceRequest, StateTransition, RoutingHandshake, SettlementNotice, AuditProbe, ResearchWorkflow, ModelWeights) that determines which adapters must run and what is hashed into the audit record.

Research Workflow Bundle

A typed bundle carrying a research-agent workflow definition — experimental design, benchmark specification, routing policy, and privacy tier — for execution on the distributed inference fabric. Requires researcher-tier enrollment and inherits research-data compliance.

Model Weights Bundle

A typed bundle carrying model weight artifacts for research agents. Verified against a pinned SHA-256 hash signed by the DOSFI model registry authority before execution. Prevents model spoofing and supply-chain substitution.

Transport Lifecycle

The seven deterministic phases (INIT, SUBMIT, ACCEPT, ROUTE, PRICE, COMMIT, DELIVER, ACK) plus DROPPED, DEFERRED, FAILED terminal edges; forward edges only.

DIU Metering

The algorithm mapping verified runtime execution receipts to metered DIU via ops, model weight, price scale, and the hard-cap window; unverified receipts yield zero.

DIU Price Scaling

Deterministic scaling of metered compute to DIU using published base_rate and bounded demand and supply factors, capped so issuance never exceeds the remaining window budget.

Settlement Protocol

The MeshNativeExchange subsystem set (meterer, pricer, ledger, binder) that finalizes compute-backed DIU issuance from transport quotes and audit records.

Two-Phase Issuance

The prepare to commit or rollback ledger discipline guaranteeing exactly-once, lock-protected DIU issuance with auto-rollback on timeout.

Routing Policy Score

The normalized weighted sum of trust, geo-compliance, capacity, latency, and operator preference used by the Routing adapter to order the destination set.

Trust Score

An identity-derived value in [0,1] reflecting the verified standing of a node's @dosfi.ai identity, used as a weight in routing.

Geo-Compliance

A binary signal asserting a node's residency class contains the payload's required residency class; a 0 cannot be overridden by any other weight.

Transport Integrity

The property that the audit chain is append-only and is re-evaluated by MeshInfer.AI against learned invariants; breaches quarantine the bundle.

MeshNativeExchange (MNE)

The compute-backed settlement layer (MeshNativeExchange.com) that finalizes Vital (DIU) issuance from transport quotes via the settlement protocol.

Identity Adapter

The first-running transport adapter that verifies the sender identity token, checks revocation, and projects the privacy tier for the rest of the lifecycle; read-only on payload.

Privacy Adapter

The second-running adapter that enforces the privacy tier and is the sole writer of allowed_destinations; no later adapter may expand that set.

Audit Adapter

The terminal adapter that writes exactly one append-only, tamper-evident record per phase transition; a fault here hard-fails the phase.