§ NEW · Unified Ecosystem Architecture
The Distributed Intelligence Stack — one theory, five systems.
MeshInfer.AI is the central inference fabric that unifies DOSFI, MeshNativeExchange, DOSFI Academy, and DOSFI University into a single, coherent platform for distributed intelligence. This document is the authoritative architectural reference for all five systems.
Syncing ecosystem state…
U.0
Unification Status — all five platforms
The Mesh-Native Unifying Theory is structurally enforced across every platform in the Distributed Intelligence Stack. The badge below confirms all 11 theory components are active; the compliance maps that follow show how each of the five systems realizes them.
U.1
The Mesh-Native Unifying Theory of Distributed Intelligence
The Mesh-Native Unifying Theory of Distributed Intelligence holds that intelligence — the execution of inference, reasoning, and decision-making — should run on the compute that already exists in the world: in users' devices, in peer networks, and in the cloud as a last resort. The five systems of the Distributed Intelligence Stack are the engineering realization of this theory.
The single authoritative definition
Distributed intelligence is the practice of routing, executing, and settling AI inference workloads across heterogeneous compute — local devices, peer mesh nodes, and cloud providers — governed by a unified identity layer, metered in a compute-backed economic unit (the Distributed Intelligence Unit, DIU), and settled on a transparent exchange — such that any application can access intelligence at the lowest cost, lowest latency, and highest privacy that the available compute allows.
The five-system architecture
topology
┌─────────────────────────────────────────────────────────────────────────────┐
│ DISTRIBUTED INTELLIGENCE STACK — LAYER MODEL │
├─────────────────────────────────────────────────────────────────────────────┤
│ LAYER 5 · EDUCATION & CERTIFICATION │
│ ┌─────────────────────────────┐ ┌──────────────────────────────────────┐ │
│ │ DosfiAcademy.com │ │ DosfiUniversity.com │ │
│ │ Developer Onboarding │ │ Enterprise Certification │ │
│ │ SDK labs · routing labs │ │ Architect tiers · DIU economics │ │
│ └──────────────┬──────────────┘ └─────────────────┬────────────────────┘ │
├─────────────────┼───────────────────────────────────┼──────────────────────┤
│ LAYER 4 · ECONOMIC SETTLEMENT │ │
│ ┌──────────────▼─────────────────────────────────────▼──────────────────┐ │
│ │ MeshNativeExchange.com │ │
│ │ Vital DIU issuance · compute spend accounting · epoch settlement │ │
│ └────────────────────────────────┬───────────────────────────────────────┘ │
├───────────────────────────────────┼─────────────────────────────────────────┤
│ LAYER 3 · INFERENCE FABRIC ◄────┼──── THIS IS WHERE EVERYTHING FLOWS ──── │
│ ┌────────────────────────────────▼───────────────────────────────────────┐ │
│ │ MeshInfer.AI — Central Inference Fabric │ │
│ │ Routing · Scheduling · Privacy enforcement · Metering · DIU events │ │
│ └────────────────────────────────┬───────────────────────────────────────┘ │
├───────────────────────────────────┼─────────────────────────────────────────┤
│ LAYER 2 · DISTRIBUTED OS │
│ ┌────────────────────────────────▼───────────────────────────────────────┐ │
│ │ DOSFI.ai — Mesh Operating System │ │
│ │ Runtime · Scheduler · Identity · Privacy model · Protocol │ │
│ └────────────────────────────────┬───────────────────────────────────────┘ │
├───────────────────────────────────┼─────────────────────────────────────────┤
│ LAYER 1 · COMPUTE │
│ ┌──────────────┐ ┌─────────────┐ ┌─────────────┐ ┌────────────────────┐ │
│ │ Browser │ │ Desktop │ │ Mobile │ │ Server / Cloud │ │
│ │ WebGPU/WASM │ │ llama.cpp │ │ CoreML/ │ │ CUDA / bare-metal │ │
│ │ nodes │ │ nodes │ │ NNAPI nodes│ │ nodes │ │
│ └──────────────┘ └─────────────┘ └─────────────┘ └────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────┘
Each system's role — canonical definitions
U.2
The Unified Architecture Narrative
The authoritative one-paragraph story — consistent across all five systems
Applications run on DOSFI, the distributed operating system that manages runtime, scheduling, identity, and privacy for mesh-native workloads. Inference flows through MeshInfer.AI, the central fabric that routes each request to the optimal compute target — local, peer mesh, or cloud — metering every token against the requester's account. Compute is quantified in Distributed Intelligence Units (DIU), issued to nodes on task completion and spent by applications on task dispatch, then settled transparently on MeshNativeExchange in hourly epochs. Developers learn this stack at DOSFI Academy, building real inference applications in hands-on SDK labs. Engineering leaders certify on it at DOSFI University, completing architect-tier curricula in distributed inference engineering, DIU economics, and production mesh operations.
The data flow — end to end
sequence
Developer App (DOSFI Runtime)
│
│── "infer(prompt, model, policy)" ──────────────────────────────────►
│ │
│ MeshInfer.AI Coordinator │
│ ┌─────────────────────────────────┐ │
│ │ 1. Identity verification │ │
│ │ (DOSFI identity token) │ │
│ │ 2. Privacy gate │ │
│ │ (policy: local_only/mesh_ok) │ │
│ │ 3. Routing decision │ │
│ │ (local → mesh → cloud) │ │
│ │ 4. Task dispatch to node │ │
│ │ 5. Metering event emitted │ │
│ │ → DIU spend debited │ │
│ └─────────────────────────────────┘ │
│ │ │
│ Node executes inference │
│ ┌─────────────────────────────────┐ │
│ │ 6. Tokens generated │ │
│ │ 7. Result returned (encrypted) │ │
│ │ 8. DIU issuance event emitted │ │
│ └─────────────────────────────────┘ │
│ │ │
│ MeshNativeExchange (hourly epoch) │
│ ┌─────────────────────────────────┐ │
│ │ 9. Batch issuance events │ │
│ │ 10. Integrity verify │ │
│ │ 11. Commit wallet credits │ │
│ │ 12. Settlement log → AuditLog │ │
│ └─────────────────────────────────┘ │
│◄──── tokens streamed back ────────────────────────────────────────────│U.3
DOSFI.ai → MeshInfer.AI Integration
Every interaction between DOSFI and MeshInfer is governed by a formal integration contract. The four DOSFI subsystems each have defined responsibilities within the MeshInfer fabric.
DOSFI Runtime → MeshInfer inference routing
| Contract | DOSFI Runtime calls MeshInfer via the @meshinfer/sdk. Every inference call passes through MeshInfer routing — no direct cloud calls are made by the Runtime. |
| Runtime responsibility | Execute inference locally when the routing decision is local. Stream tokens back to the calling application. |
| MeshInfer responsibility | Issue the routing decision (local / mesh / cloud), enforce the privacy gate, and dispatch the task to the selected compute target. |
| Failure handling | If local runtime fails, MeshInfer re-routes to mesh or cloud within the configured fallback policy. DOSFI Runtime reports the failure via the heartbeat. |
DOSFI Scheduler → MeshInfer scheduling
| Contract | DOSFI Scheduler sets per-node task concurrency caps and priority classes. MeshInfer Coordinator respects these caps when dispatching from the NATS task queue. |
| Scheduler responsibility | Report active_tasks count in every heartbeat. NACK tasks that would exceed the cap. Signal preemption readiness for background tasks. |
| MeshInfer responsibility | Dispatch tasks to the correct internal queue partition. Honor NACK responses by immediately re-dispatching to the next-best node. |
| Priority integration | DOSFI Scheduler exposes priority hints (interactive / standard / background) which MeshInfer uses to select queue partition and latency SLO. |
DOSFI Identity & Privacy → MeshInfer enforcement
| Contract | The DOSFI OIDC token is the only accepted authorization credential for MeshInfer. Routing permissions, model access scope, and privacy tiers are all claims within the token. |
| Privacy gate (synchronous) | MeshInfer evaluates the privacy_policy claim from the token BEFORE any I/O — no data ever leaves the device on a local_only policy, regardless of downstream behavior. |
| Node cert binding | NodeID cert must match the identity-bound DeviceID. Mismatched certs result in immediate 401 rejection at the MeshInfer Gateway. |
| Tier enforcement | Subscription tier claim in the token gates model access: developer (local only), startup (mesh routing), growth (BYOM, advanced policies), enterprise (on-prem, HIPAA BAA). |
DOSFI Storage → MeshInfer state transitions
| Inference state | Active task state (task_id, model, tokens_generated, checkpoint) is stored ephemerally by MeshInfer for KV-cache transfer in V3. |
| Model cache | DOSFI Storage layer hosts the local model cache. MeshInfer reads model_warm status from the capability vector — which is derived from the DOSFI Storage inventory. |
| Routing log persistence | MeshInfer writes RoutingLog records (route_decision, node_id, latency_ms, tokens) to the DOSFI-backed entity store for analytics and billing. |
| Audit trail | Every metering, issuance, and settlement event is written to the AuditLog entity — the DOSFI-backed audit store — for SOC 2 compliance. |
U.4
MeshNativeExchange.com → MeshInfer.AI Integration
DIU spend triggered by MeshInfer metering
| Trigger | MeshInfer Billing Meter emits a metering_event to Kafka on every completed inference task. |
| Spend calculation | diu_spend = (tokens_out / 1000) × RATES[req_class][route_decision]. Rates are set by the DOSFI pricing oracle and updated at each billing period. |
| Wallet debit | OrgID requester wallet is debited atomically with the metering event. Zero DIU balance → task dispatch blocked. No credit → no compute. |
| Exchange role | MeshNativeExchange receives spend events as inputs to the settlement batch. It does not calculate spend — it validates and commits what MeshInfer reports. |
DIU issuance triggered by inference execution
| Trigger | MeshInfer emits a diu_issued event for every successfully completed task. Failed tasks and late tasks (> 3× SLO) yield zero issuance. |
| Issuance formula | diu_net is derived from diu_spend, adjusted by the node's reputation and quality multipliers. The gross spend is split between the node wallet, platform infrastructure, and protocol reserve, with the majority going to the node. |
| Exchange role | MeshNativeExchange batches pending issuance events at each hourly epoch, verifies integrity (SHA-256 hash chain), and commits final credits to node wallets. |
| Audit | Every issuance event is written to AuditLog with resource_type: "diu_issued". Settlement records carry an integrity_hash verifiable externally. |
Settlement logs originate from MeshInfer
| Source of truth | MeshInfer is the sole source of settlement input data. MeshNativeExchange is the settlement executor — it does not generate its own compute events. |
| Log fields | settlement_id, epoch_start, epoch_end, node_settlements[], total_diu_issued, total_platform_fee, integrity_hash, committed_at |
| Dispute resolution | If a node disputes a settlement, the dispute references a specific request_id in MeshInfer RoutingLog. MeshInfer logs are the arbitration source. |
U.5
DOSFI Academy & University → MeshInfer.AI Integration
DosfiAcademy.com — developer onboarding via MeshInfer
DosfiUniversity.com — enterprise certification via MeshInfer
U.6
Cross-System Consistency Layer
The following terminology, architectural language, and system descriptions are the canonical versions. Every document, UI, and communication across all five systems must use these definitions without modification.
Unified terminology guide
Unified navigation & cross-link map
U.7
MeshInfer-Centric Integration Map
topology
┌────────────────────────────────────────────────┐
│ MeshInfer.AI (Central Hub) │
│ │
DOSFI.ai ────────────►│ ┌──────────┐ ┌──────────┐ ┌─────────────┐ │
(Runtime, Scheduler, │ │ Gateway │ │ Router │ │ Task Queue │ │
Identity, Storage) │ │ (CF Edge)│ │ Engine │ │ (NATS JS) │ │
│ └──────────┘ └──────────┘ └─────────────┘ │
DosfiAcademy.com ────►│ ┌──────────┐ ┌──────────┐ ┌─────────────┐ │
(SDK labs, routing │ │ Identity │ │ Billing │ │ Reputation │ │
tutorials, metering) │ │ Verifier │ │ Meter │ │ Scorer │ │
│ └──────────┘ └────┬─────┘ └──────┬──────┘ │
DosfiUniversity.com ──►│ │ │ │
(architecture courses, │ ▼ ▼ │
certification, DIU) │ DIU Spend Node Pool │
│ Events │
└────────────────────┬───────────────────────────┘
│
┌────────────────────▼───────────────────────────┐
│ MeshNativeExchange.com │
│ Issuance events · Epoch settlement · Wallets │
└────────────────────────────────────────────────┘
│
┌──────────────────┬──────────────┴──────────────┬────────────────────┐
▼ ▼ ▼ ▼
node-d01…d08 node-b01…b06 node-m01…m04 node-s01…s02
Desktop tier Browser tier Mobile tier Server tier
llama.cpp WebGPU / WASM CoreML / NNAPI CUDA 12+
Integration contract summary
Document maintenance
This document is the single source of truth for ecosystem architecture. When any of the five systems updates its architecture, this document must be updated in the same release. All five system documentation sites must reference this document as the canonical architecture narrative (adapted to their audience, never contradicting it).