DOSFI Mesh-Native Transport Layer
The public transport interface for mesh-native distribution of bundles — model weights, datasets, app bundles, workflows, routing policies, UI schemas, and storage schemas — across the global mesh, integrated with DOSFI Foundations and MeshInfer.AI.
A subsystem of DOSFI, not a separate network.
The DOSFI Mesh-Native Transport Layer is the published interface for moving bundles across the mesh. It operates above the ABI boundary, exposing five conceptual adapters that enforce identity, privacy, routing, economics, and audit policy. The transport layer is not a standalone protocol — it is governed by the same DOSFI Foundations that govern compute and storage.
Mesh-Native by Design
Transfers route across the same peer mesh that executes compute — no separate delivery network.
Bundle-Centric
Every transfer is a typed bundle with metadata, privacy tier, identity requirements, and integrity checksum.
Workflow-Executable
The transport layer emits mesh-native workflow definitions that the DOSFI state machine executes across nodes.
Built on DOSFI Foundations.
The transport layer integrates with every DOSFI Foundation. No transfer occurs outside the identity fabric, privacy tier model, routing policy, scheduler, storage schema, or workflow state machine.
DOSFI Identity Fabric
Every transport operation is bound to an attested @dosfi.ai identity. The Identity Adapter signs and verifies all envelopes.
DOSFI Privacy Tier Model
Tier 0–Tier 5 classification governs peer eligibility, encryption, and attestation requirements for every bundle.
DOSFI Routing Policy
The Routing Adapter applies routing policy for peer selection, geo-compliance, and multi-hop relay negotiation.
DOSFI Scheduler
Relay capacity and transfer prioritization are coordinated alongside compute workloads across the mesh.
DOSFI Storage Schema
Bundles reference content via the DOSFI storage schema, enabling deduplication, replication, and locality-aware retrieval.
DOSFI Workflow + State Machine
The transport layer emits a mesh-native workflow definition that the DOSFI state machine executes across nodes.
Seven bundle types. One transport.
The transport layer moves any typed bundle across the mesh. Each bundle type carries its own validation rules but shares a common envelope schema.
Model Weights
Distributed inference model parameters, sharded for mesh transport.
Datasets
Training, validation, and inference datasets with privacy tier classification.
Mesh-Native App Bundles
Complete application packages built on the DOSFI app runtime.
Workflow Definitions
Multi-step workflow specs executable by the DOSFI state machine.
Routing Policies
Operator-defined routing rules and peer selection constraints.
UI Schemas
Declarative UI definitions for mesh-native app frontends.
Storage Schemas
Distributed storage layout and replication definitions.
Five adapters govern every transfer.
Each adapter is a sealed DOSFI subsystem that enforces one dimension of transport policy. Adapters execute in sequence during each transfer lifecycle — identity first, then privacy, routing, economics, and audit.
Identity Adapter
Binds every transport operation to the DOSFI Identity Fabric (@dosfi.ai). Verifies peer identity, signs bundle envelopes, and enforces identity-scoped access control before any transfer begins.
- Resolve @dosfi.ai identity for sender and receiver peers
- Sign bundle envelopes with attested node identity keys
- Enforce identity-scoped ACLs on bundle access and relay
- Reject unsigned or identity-mismatched transfer requests
Privacy Adapter
Enforces the DOSFI Privacy Tier Model (Tier 0–Tier 5) on every bundle. Determines the required tier from bundle metadata and gates peer eligibility accordingly.
- Classify bundle privacy tier (T0–T5) from metadata
- Filter candidate peers to those satisfying the tier policy
- Apply post-quantum encryption for Tier 2 and above
- Enforce hardware attestation requirements for sealed tiers
Routing Adapter
Uses the DOSFI Routing Policy for peer selection and multi-hop relay. Optimizes path selection for latency, trust, and privacy tier compliance.
- Evaluate candidate relay paths against routing policy
- Select peers by trust score, geo-compliance, and capacity
- Negotiate multi-hop transfer agreements across the mesh
- Re-route on peer failure or trust-score degradation
Economics Adapter
Meters compute and bandwidth consumed by each transfer. Calculates the DIU cost of a bundle transfer and coordinates Vital DIU issuance and spend across participants.
- Meter bandwidth (bytes transferred) and relay compute (cycles)
- Quote DIU cost for bundle transport before transfer begins
- Coordinate DIU escrow, spend authorization, and settlement
- Apply operator-defined pricing and incentive multipliers
Audit Adapter
Writes every transport event — transfer initiation, peer selection, tier enforcement, DIU settlement, completion — to the DOSFI audit log for MeshNativeExchange settlement and compliance.
- Emit signed audit events for each transport lifecycle stage
- Append to the immutable DOSFI audit ledger
- Correlate transport events with MNE settlement records
- Surface audit proofs for enterprise compliance and dispute resolution
Seven phases. Zero ambiguity.
Every transfer moves through seven ordered phases. Each phase is audited, and no phase may begin until the prior phase's adapters have signed off.
Bundle Authoring
A node or operator authors a bundle, attaches metadata, selects a privacy tier, and computes the integrity checksum. The Identity Adapter signs the envelope.
Tier Enforcement
The Privacy Adapter evaluates the bundle's privacy tier and filters the candidate peer set. Peers failing the tier policy are excluded before any negotiation.
Peer Selection
The Routing Adapter selects an optimal relay path from the filtered peer set using DOSFI Routing Policy: trust, latency, geo-compliance, and capacity.
Economics Quote
The Economics Adapter meters the estimated transfer cost and quotes a DIU price. The sender authorizes DIU spend (or sponsors the transfer). Escrow is established.
Transfer
The bundle streams across the selected relay path over post-quantum encrypted channels. Each relay verifies identity and tier before forwarding.
Integrity Verification
The receiver recomputes the checksum and verifies the signature. MeshInfer.AI may be invoked for inference-based anomaly detection or content validation.
Audit & Settlement
The Audit Adapter writes signed events to the DOSFI audit ledger. The Economics Adapter finalizes DIU settlement via MeshNativeExchange. Relays and receiver are paid.
The bundle envelope.
Every bundle carries a typed envelope. The schema is the stable contract between the transport layer, the adapters, and the DOSFI Foundations.
| Field | Type | Required | Description |
|---|---|---|---|
| bundle_id | string (UUIDv7) | Yes | Globally unique, time-ordered identifier for the bundle. UUIDv7 ensures sortability by creation time for log correlation. |
| bundle_type | enum | Yes | One of: model_weights | dataset | app_bundle | workflow_definition | routing_policy | ui_schema | storage_schema. |
| metadata | object | Yes | Arbitrary key-value metadata: author, version, created_date, content_hash, parent_bundle_id, description, labels. |
| privacy_tier | enum (T0–T5) | Yes | Privacy tier classification from the DOSFI Privacy Tier Model. Determines peer eligibility and encryption requirements. |
| identity_requirements | object | Yes | Required sender/receiver identity attributes: min_trust_score, required_claims, allowed_roles, geo_allowlist. |
| routing_hints | object | No | Optional routing preferences: preferred_regions, max_hops, latency_target, preferred_peers, avoid_peers. |
| diu_cost | object | Yes | Economics metadata: estimated_bandwidth_bytes, relay_compute_estimate, diu_price, payment_mode (escrow | direct | sponsored). |
| integrity_checksum | object | Yes | Content integrity: sha256 checksum, merkle_root (for sharded bundles), signature (node identity signature over the envelope). |
| payload_ref | string (URI) | Yes | Reference to the bundle payload — either an inline content-addressed hash or a DOSFI storage schema URI. |
A workflow DOSFI can execute across nodes.
The transport layer emits a mesh-native workflow definition that the DOSFI Workflow + State Machine engine executes. Each transfer is a workflow instance with a defined state machine.
Bundle created, signed, and ready for dispatch.
Identity and tier enforcement complete; peer selection begins.
Routing Adapter evaluates relay paths and selects peers.
DIU cost quoted and sender authorization captured.
DIU escrow established; transfer authorized to begin.
Bundle streaming across relay path; progress events emitted.
Receiver validates checksum and signature; optional MeshInfer validation.
Audit written, DIU settled via MNE, transfer complete.
Terminal failure — identity or tier enforcement blocked the transfer.
Terminal failure — no compliant relay path found.
Terminal failure — sender denied DIU spend.
Terminal failure — transfer interrupted; escrow refunded.
Terminal failure — checksum or signature mismatch; escrow refunded.
Routing policy, not routing guesswork.
The Routing Adapter applies the DOSFI Routing Policy to select peers and relay paths. Selection is deterministic, audited, and re-evaluated on every hop.
Candidate Pool
Collect all peers currently reachable from the sender, excluding any peer that fails the Privacy Adapter's tier filter.
Policy Scoring
Score each candidate against the routing policy: trust score, geo-compliance, current capacity, latency estimate, and operator preferences.
Path Construction
Construct a relay path (single-hop or multi-hop) that satisfies the bundle's routing hints — max hops, latency target, preferred regions.
Economics Check
Verify the selected path's DIU cost is within the sender's authorized spend. Re-select a cheaper path if the quote exceeds budget.
Reservation
Reserve capacity on each relay along the path. Relay availability is confirmed before transfer begins.
Re-Evaluation
On each hop and on any trust-score change, the Routing Adapter re-evaluates the remaining path and may re-route mid-transfer.
Metered transport. DIU-settled.
The Economics Adapter meters every transfer and coordinates Vital DIU issuance and spend via MeshNativeExchange. Transport is not free — relays and receivers earn DIU, senders spend DIU.
Bandwidth Metering
Bytes transferred are metered per hop. The DIU price scales with bandwidth consumed and the bundle's privacy tier.
Relay Compute Metering
Relay compute cycles (encryption, verification, forwarding) are metered and priced in DIU alongside bandwidth.
Escrow & Authorization
Before transfer, the sender authorizes DIU spend into escrow. Escrow is released on settlement or refunded on failure.
MNE Settlement
On successful transfer, the Economics Adapter finalizes settlement via MeshNativeExchange — relays and receiver are paid in DIU.
Every transfer. Every event. Immutable.
The Audit Adapter writes signed events to the DOSFI audit ledger for every transport lifecycle stage. Audit records are the basis for MNE settlement, enterprise compliance, and dispute resolution.
Bundle authored and dispatch requested. Includes bundle_id, sender identity, privacy tier.
Privacy Adapter completed tier filtering. Records the candidate peer set before and after filtering.
Routing Adapter selected a relay path. Records the path, peers, and policy scores.
Economics Adapter quoted a DIU cost and sender authorized spend.
DIU escrow established. Records escrow ID and amount.
Each relay forwards the bundle. Records relay identity and hop index.
Receiver validated checksum and signature. Records verification result.
DIU settled via MNE. Records settlement ID and participant payouts.
Terminal failure. Records failure reason, escrow refund, and affected peers.
Inference-powered transport integrity.
The transport layer integrates with MeshInfer.AI for inference-based validation, anomaly detection, integrity verification, and routing optimization.
Inference-Based Validation
MeshInfer.AI runs lightweight inference on received bundles (e.g. model weight sanity, dataset distribution checks) to validate content semantics before settlement.
Anomaly Detection
MeshInfer.AI inspects transfer telemetry and bundle metadata patterns to flag anomalous or potentially malicious transfers for audit review.
Integrity Verification
MeshInfer.AI cross-verifies integrity checksums and can reconstruct sharded bundles for deep content verification beyond simple hashing.
Routing Optimization
MeshInfer.AI models relay path performance and recommends route adjustments to the Routing Adapter for latency and cost optimization.
Zero-trust transport.
The transport layer inherits the DOSFI zero-trust posture. No transfer is trusted by default — identity, privacy tier, integrity, and audit are all enforced before, during, and after every transfer.
Identity-Bound Transfers
Every bundle is signed by an attested @dosfi.ai identity. Transfers between identity-mismatched peers are rejected at the relay.
Post-Quantum Encryption
All transfers at Tier 2 and above use lattice-based post-quantum encryption. Keys are derived from attested node identity and never persisted.
Tier-Gated Access
Privacy tier enforcement happens before peer selection — no non-compliant peer can even negotiate a transfer.
Immutable Audit Trail
Every transport event is written to the DOSFI audit ledger with a signed proof, enabling MNE settlement and enterprise compliance.
Anomaly Detection
MeshInfer.AI continuously monitors transfer patterns and flags anomalies for audit review and potential escrow hold.
Replay & Tamper Protection
UUIDv7 bundle IDs, monotonic sequence numbers, and content checksums prevent replay, tampering, and substitution attacks.
One transport interface. Three systems. Zero divergence.
The DOSFI Mesh-Native Transport Layer is fully unified across DOSFI.ai, MeshInfer.ai, and MeshNativeExchange.com. All three systems share a consistent transport interface for mesh-native distribution of model weights, datasets, app bundles, workflows, routing policies, UI schemas, and storage schemas.
DOSFI.ai
Owns the transport interface specification, the five adapters, and the Foundations (Identity, Policy, Privacy/Data, Observability). DOSFI defines the bundle envelope schema and adapter contracts that all three systems implement.
- Defines the transport API and bundle envelope schema
- Hosts the five adapters (Identity, Privacy, Routing, Economics, Audit)
- Governs the four Foundations fabrics
- Publishes the ABI boundary contract
MeshInfer.ai
Consumes the transport interface for model weight distribution and workflow execution. MeshInfer.AI routes inference workloads through the same transport layer — it does not implement a parallel delivery path.
- Receives model_weights bundles via the transport layer
- Executes workflow_definition bundles on the mesh
- Respects sharding metadata and privacy tier constraints
- Triggers policy enforcement and audit logging on every bundle
MeshNativeExchange.com
Distributes app bundles, workflows, and routing policies through the same transport layer. Permission Manifests align with transport metadata, and developer publishing uses the unified interface.
- Distributes app_bundle and ui_schema bundles via transport
- Aligns Permission Manifests with transport metadata
- Settles DIU economics through the Economics Adapter
- Correlates audit events for compliance and dispute resolution
All six criteria verified.
The transport layer has been evaluated against six integration criteria. Every criterion is satisfied — the transport interface is consistent, compliant, and unified across all three systems.
All seven bundle types. All three systems.
Every bundle type flows through the same transport interface. Each system plays its role — DOSFI defines, MeshInfer consumes or validates, MeshNativeExchange distributes — but the envelope schema and adapter enforcement are identical.
| Bundle Type | DOSFI.ai | MeshInfer.ai | MeshNativeExchange | Unified |
|---|---|---|---|---|
model_weights | Defines schema | Primary consumer | Distributes | Yes |
dataset | Defines schema | Validates & shards | Distributes | Yes |
app_bundle | Defines schema | — | Primary distributor | Yes |
workflow_definition | Defines schema | Executes | Distributes | Yes |
routing_policy | Defines & enforces | Respects constraints | Distributes | Yes |
ui_schema | Defines schema | — | Primary distributor | Yes |
storage_schema | Defines schema | Respects for sharding | Distributes | Yes |
Every bundle inherits all four frameworks.
Compliance is not bolted on — it is inherited. The transport layer binds to the four DOSFI Foundations fabrics, which enforce NIST 800-63B, SOC 2, HIPAA, and GDPR on every bundle movement across all three systems. No transfer can bypass compliance enforcement.
NIST 800-63B
Identity assurance levels enforced by the Identity Adapter on every transfer.
SOC 2
Security, availability, and confidentiality controls inherited via the Observability Fabric audit trail.
HIPAA
PHI-safe routing rules enforced by the Privacy Adapter — sealed tiers require hardware attestation.
GDPR
Purpose limitation, consent, and data-subject routing constraints enforced by the Policy Fabric.