Hands-on exercises on the open surface
DOSFI Labs are practical exercises built entirely on public SDKs, documented APIs, and open-surface materials. Every lab preserves the sovereign closed-core / open-surface boundary.
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.
Lab Exercises
Lab 01 — SDK Setup & Authentication
Objective: Install the DOSFI SDK, configure an API key, and verify connectivity using the public health endpoint.
Steps
- 01Install the @dosfi/sdk package from the public registry
- 02Create a test API key from the MeshNativeExchange developer portal
- 03Initialize the SDK client with your key
- 04Call the public health check endpoint to verify connectivity
Verification: A successful health-check response confirms your SDK is correctly configured.
Sovereignty boundary: This lab uses only the public SDK and documented endpoints. No internal authentication or runtime logic is exposed.
Lab 02 — Submitting Your First Workload
Objective: Submit a Standard-tier inference workload through the public SDK and inspect the returned result and spend record.
Steps
- 01Construct a workload request with model, prompt, and token budget
- 02Set privacyTier to 'standard' via the public API parameter
- 03Submit the workload and await the result
- 04Inspect the output, vitalConsumed, and settlementRef fields
Verification: The response includes a non-null output, a positive vitalConsumed value, and a settlementRef string.
Sovereignty boundary: Workload routing and scheduling internals are closed-core. This lab covers only the public submission API.
Lab 03 — Querying Billing & Spend Records
Objective: Use the public billing API to retrieve a billing period summary and parse the spend record schema.
Steps
- 01Call dosfi.billing.getPeriod with a target period label
- 02Inspect routingUnits, storageUnits, inferenceUnits, and vitalConsumed
- 03Extract the settlementRef for MeshNativeExchange reconciliation
- 04Validate the record against the documented public schema
Verification: The billing summary matches your submitted workloads and the settlementRef is a valid string.
Sovereignty boundary: Billing aggregation internals are not disclosed. Only the public billing API and documented schema are used.
Lab 04 — Privacy Tier Selection
Objective: Submit identical workloads under Standard, Confidential, and Sovereign tiers and compare the resulting Vital spend.
Steps
- 01Submit the same workload three times, varying only the privacyTier parameter
- 02Record the vitalConsumed value for each submission
- 03Calculate the observed multipliers and compare to documented rates (1.0×, 1.8×, 3.2×)
- 04Document which tier is appropriate for different workload classes
Verification: Observed multipliers approximately match the documented public billing rates.
Sovereignty boundary: Privacy enforcement internals are sovereign and closed. This lab observes only the public billing surface.
Lab 05 — Settlement Integration with MeshNativeExchange
Objective: Forward a DOSFI spend record to MeshNativeExchange and initiate a fiat redemption.
Steps
- 01Retrieve a billing period summary from DOSFI (Lab 03 output)
- 02Submit the settlementRef to the MeshNativeExchange redemption API
- 03Monitor the redemption status via the public status endpoint
- 04Confirm fiat settlement completion and record the reference
Verification: The redemption record transitions from 'initiated' to 'completed' and a fiat settlement reference is returned.
Sovereignty boundary: Settlement engine and reconciliation internals are closed-core. This lab uses only public APIs on both sides.