Runtime Mesh Metadata Synchronization
Local verification that WebGPU, CoreML, ONNX Runtime, llama.cpp, and the Browser Task Worker have loaded the updated mesh metadata and are operating under the unified mesh context — eligible for unified dispatch.
5 / 5
Runtimes Synced
9 / 9
Metadata Fields Loaded
Unified
Dispatch Eligibility
GooD To Go
Final Status
Five Runtime Platforms
Each runtime has loaded the updated mesh metadata and confirmed readiness for unified dispatch. All runtimes operate in local-first mode with mesh-awareness — no cross-node synchronization attempted.
WebGPU
Browser GPU Compute
2026-07-18T01:08:42Z
Ready
Registered
Compatible
Browser → GPU Shader → Mesh Dispatch → Settlement
Mesh Metadata Loaded
node_webgpu_0x1a2b
GPU compute · shader dispatch · WGSL
us-east-1
0.85
Gold
sub-50ms
99.7%
Local-first · mesh-aware
Standard tier · $0.0012/credit
CoreML
Apple Device ML
2026-07-18T01:08:38Z
Ready
Registered
Compatible
Device → Neural Engine → Mesh Dispatch → Settlement
Mesh Metadata Loaded
node_coreml_0x3c4d
Neural Engine · GPU · ANE
us-west-2
0.78
Gold
sub-30ms
99.9%
Local-first · mesh-aware
Confidential tier · $0.0025/unit
ONNX Runtime
Cross-Platform ML
2026-07-18T01:08:45Z
Ready
Registered
Compatible
Runtime → ONNX Model → Mesh Dispatch → Settlement
Mesh Metadata Loaded
node_onnx_0x5e6f
CPU · GPU · NPU · EP
eu-west-1
0.82
Gold
sub-40ms
99.8%
Local-first · mesh-aware
Standard tier · $0.0012/credit
llama.cpp
Local LLM Inference
2026-07-18T01:08:40Z
Ready
Registered
Compatible
Local CPU/GPU → GGUF Model → Mesh Dispatch → Settlement
Mesh Metadata Loaded
node_llamacpp_0x7g8h
CPU · GPU · GGUF · quantized
us-east-1
0.75
Silver
sub-100ms
99.5%
Local-first · mesh-aware
Standard tier · $0.0008/unit
Browser Task Worker
Background Browser Compute
2026-07-18T01:08:44Z
Ready
Registered
Compatible
Service Worker → Background Task → Mesh Dispatch → Settlement
Mesh Metadata Loaded
node_worker_0x9i0j
Service Worker · WASM · background
us-east-1
0.70
Silver
sub-80ms
99.6%
Local-first · mesh-aware
Standard tier · $0.0005/unit
Mesh Metadata Fields Loaded
All nine mesh metadata fields have been loaded across all five runtimes. Each field is verified present and consistent with the unified mesh context.
Metadata Field
Runtimes Loaded
Status
node identity
5 / 5
Loaded
runtime capabilities
5 / 5
Loaded
region assignment
5 / 5
Loaded
dispatch weight
5 / 5
Loaded
reputation tier
5 / 5
Loaded
latency profile
5 / 5
Loaded
verification rate
5 / 5
Loaded
scheduler state
5 / 5
Loaded
privacy and cost policies
5 / 5
Loaded
Unified Dispatch Compatibility
Runtime Status
All five runtimes report Active status with current heartbeats within the last 10 seconds. No runtime is degraded, offline, or in a fault state.
Readiness State
All five runtimes report Ready readiness. Each runtime has completed local initialization and is prepared to accept dispatch tasks.
Task Worker Registration
All five runtimes have Registered task workers with the local scheduler. Workers are bound to their respective node identities and ready for workload assignment.
Inference Dispatch Compatibility
All five runtimes are Compatible with the unified dispatch protocol. MeshInfer execution paths are validated end-to-end through the transport layer to settlement.
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.