Ecosystem Synced·11 Articles7 Rules5 Actions5 Continuity Plans0 Supra-Signals
DOSFI Academy

Courses for the Distributed Intelligence Stack

DOSFI Academy provides structured learning paths built exclusively on open-surface materials — SDKs, documentation, and public APIs. All courses preserve the sovereign closed-core / open-surface model.

DOSFI Sovereignty — Closed Core / Open Surface

DOSFI Core is sovereign and closed. All educational content on this page is generated exclusively from open-surface materials — SDKs, ABIs, documentation, tutorials, examples, and conceptual explanations. Internal details of the DOSFI Runtime, Scheduler, Router, Readiness Engine, Privacy Model, Power/Thermal Model, Vital internals, DIU internals, MNE internals, and Mesh-Native App runtime internals are not revealed, described, or inferred.

No proprietary algorithms, system code, or architectural diagrams capable of enabling replication of the DOSFI Core are published. When internal logic is referenced, only high-level conceptual explanations are provided. DOSFI's sovereignty, mission-lock, and non-replicable architecture are preserved at all times.

Course Catalog

Foundations 2 hours 4 modules

DOSFI 101 — The Distributed OS for Intelligence

A conceptual introduction to DOSFI as the operating system layer of the Distributed Intelligence Stack. Covers the open-surface SDK, public API surface, and the relationship between DOSFI and MeshNativeExchange.

What DOSFI is — and what it is not
The open-surface model: SDKs, ABIs, and public APIs
How workloads are submitted and results returned
Vital DIU as the spend unit for compute consumption

This course covers only open-surface concepts. Internal DOSFI Runtime, Scheduler, and Router logic is not part of the curriculum.

Intermediate 3 hours 5 modules

DOSFI 201 — SDK Fundamentals

Hands-on introduction to the DOSFI SDK. Learn to authenticate, submit workloads, query billing summaries, and read spend records using the public SDK and documented APIs.

SDK installation and API key management
Submitting inference, routing, and storage workloads
Setting privacy tiers via the public API
Querying billing period summaries
Reading signed spend records for settlement

All exercises use the public SDK only. No internal runtime or scheduler internals are referenced.

Intermediate 2 hours 4 modules

DOSFI 301 — Privacy Tiers Explained

A conceptual deep-dive into the three privacy tiers — Standard, Confidential, and Sovereign — as exposed through the open API surface. Covers billing multipliers and how to select the correct tier for your workload.

Standard, Confidential, and Sovereign: what each tier means conceptually
Billing multipliers: 1.0×, 1.8×, 3.2× Vital
Selecting a tier at workload submission
Jurisdictional considerations for Sovereign workloads

Privacy tier enforcement internals are closed-core. This course covers only the public API surface and conceptual model.

Advanced 3 hours 5 modules

DOSFI 401 — Vital Settlement Integration

Connect DOSFI spend to MeshNativeExchange settlement. Learn how signed spend records flow from DOSFI to the exchange, how they are aggregated, and how fiat settlement is initiated.

Spend record structure (public schema)
Forwarding spend records to MeshNativeExchange
Aggregation across billing periods
Initiating redemption and fiat settlement
Reconciliation via the settlement API

Settlement engine internals are not covered. Only the public API and documented record formats are used.

Advanced 4 hours 6 modules

DOSFI 501 — Building Mesh-Native Applications

Architect mesh-native applications on the DOSFI open surface. Covers workload design, privacy tier strategy, cost forecasting, and integration with MeshNativeExchange for enterprise billing.

Designing workloads for the mesh
Privacy tier strategy for enterprise apps
Cost forecasting with Vital budgets
Integrating MeshNativeExchange settlement
Building resilient agent pipelines
Production readiness checklist (open-surface)

Application architecture is taught using public SDKs and documented patterns. Internal runtime behavior is not disclosed.