Ecosystem Synced·11 Articles7 Rules5 Actions5 Continuity Plans0 Supra-Signals
Mesh-Native Agent · Navigation & Coordination

Zone — Distributed Navigation, Hazard Detection & Vehicle Coordination

Zone is a mesh-native agent that runs entirely inside the mesh across DOSFI, MeshInfer, and MeshNativeExchange. It provides real-time routing, hazard detection, and multi-vehicle coordination using distributed inference — with the device acting only as renderer, sensor hub, and optional local inference node.

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.

Section 1

App Definition (DOSFI)

Workflow Pipeline
Vehicle Telemetry
speed · heading · brake · GPS
Zone Inference
distributed mesh routing
Routing Output
route · hazard · flow
Vehicle UI
CarPlay · Android Auto
State Machine
IdleZoneDiscoveryZoneJoinActiveRoutingHazardEventZoneLeave

Routing Policy

Distributed, multi-vehicle, real-time route optimization using mesh inference. Routing decisions are computed across participating nodes and reconciled via consensus — no central server required.

Execution Model

App runs inside the mesh; device acts only as renderer, sensor hub, and optional local inference node. Zero-install deployment via mesh-native bundle.

UI Schema

  • Navigation map
  • Hazard alerts
  • Route instructions
  • Zone status

Storage Schema

  • Local-first trip logs
  • Anonymized zone metrics
  • Vehicle identity token
Section 2

Inference & Intelligence (MeshInfer)

Inference Streams (Inputs)
vehicle.location
vehicle.speed
vehicle.heading
vehicle.brake_event
vehicle.traction_loss
vehicle.hazard_detected
vehicle.weather_conditions
Zone
Distributed Inference
Inference Outputs
vehicle.route
vehicle.collision_warning
vehicle.hazard_alert
vehicle.flow_instruction
vehicle.predicted_congestion
Ambient AI

Inference runs continuously across mesh nodes without requiring a central server.

Local-first Privacy

Raw vehicle telemetry never leaves the device; only anonymized aggregates enter the mesh.

Cross-device Intelligence

Vehicles, edge nodes, and cloud fallback collaborate on routing decisions.

Zero-install Computing

Zone deploys as a mesh-native bundle — no app store install or manual provisioning required.

Mesh-native Routing

Routing decisions are computed across distributed nodes and reconciled via consensus.

Section 3

Vehicle Agent (Phone App)

iOS — SwiftUI + CarPlay

Native SwiftUI app with CarPlay integration. Connects to OBD-II dongle via Bluetooth, streams telemetry to Zone, and renders routing + hazard intelligence on CarPlay display.

Android — Kotlin + Android Auto

Native Kotlin app with Android Auto integration. Mirrors iOS functionality with shared inference + mesh communication logic module for cross-platform parity.

Vehicle Agent Responsibilities

Connect to Bluetooth OBD-II dongle
Read vehicle telemetry (speed, RPM, brake, VIN, GPS)
Convert telemetry → inference streams
Publish streams to Zone
Receive routing + hazard intelligence
Render UI (CarPlay / Android Auto)

Telemetry → Inference Stream Conversion

OBD-II PID 0x0D (RPM)     → vehicle.speed
OBD-II PID 0x0C (Speed)   → vehicle.speed
OBD-II PID 0x46 (VIN)     → vehicle.identity
GPS NMEA $GPRMC           → vehicle.location, vehicle.heading
Brake pressure sensor     → vehicle.brake_event
Traction control ECU      → vehicle.traction_loss
Dashcam / lidar / radar    → vehicle.hazard_detected
Weather API + sensors     → vehicle.weather_conditions
Section 4

Zone Discovery & Membership (MNE)

Zone Metadata

NameZone
CategoryMesh-Native Navigation Agent
RegionAuto-detected via GPS
CapabilitiesRouting, hazard detection, coordination

Discovery

Vehicles query MNE for active Zones based on location. The MNE discovery API returns nearby Zones with their capabilities and membership endpoints.

Join Protocol

Vehicle sends identity token → Zone accepts membership → Vehicle begins streaming telemetry → Zone begins sending routing + hazard intelligence.

Vehicle sends identity token
Vehicle presents its cryptographic identity token to the Zone via MNE discovery.
Zone accepts membership
Zone validates the token and grants the vehicle membership in the zone.
Vehicle begins streaming telemetry
Vehicle publishes inference streams (location, speed, heading, brake, hazards) to Zone.
Zone sends routing + hazard intelligence
Zone returns route, collision warnings, hazard alerts, flow instructions, and congestion predictions.
Section 5

Deployment Requirements

DOSFI

  • App definition
  • State machine
  • Workflow
  • Routing policy

MeshInfer

  • Inference graph
  • Distributed routing engine
  • Hazard engine

MeshNativeExchange

  • Zone listing
  • Metadata
  • Discovery
  • Membership protocol
Section 6

Schemas, APIs & Message Formats

Vehicle Telemetry Schema (Inference Inputs)

{
  "vehicle.location": { "lat": "float", "lng": "float", "ts": "iso8601" },
  "vehicle.speed": { "value": "float", "unit": "kmh", "ts": "iso8601" },
  "vehicle.heading": { "degrees": "int", "ts": "iso8601" },
  "vehicle.brake_event": { "severity": "enum", "duration_ms": "int", "ts": "iso8601" },
  "vehicle.traction_loss": { "wheel": "enum", "magnitude": "float", "ts": "iso8601" },
  "vehicle.hazard_detected": { "type": "enum", "confidence": "float", "ts": "iso8601" },
  "vehicle.weather_conditions": { "condition": "enum", "visibility_m": "int", "ts": "iso8601" }
}

Routing Output Schema (Inference Outputs)

{
  "vehicle.route": { "segments": ["RouteSegment"], "eta_s": "int", "ts": "iso8601" },
  "vehicle.collision_warning": { "severity": "enum", "bearing": "int", "distance_m": "float", "ts": "iso8601" },
  "vehicle.hazard_alert": { "type": "enum", "location": "GeoPoint", "ts": "iso8601" },
  "vehicle.flow_instruction": { "action": "enum", "target_speed_kmh": "float", "ts": "iso8601" },
  "vehicle.predicted_congestion": { "segment_id": "string", "delay_s": "int", "confidence": "float", "ts": "iso8601" }
}

Zone Join Protocol Messages

// Vehicle → Zone (MNE discovery)
{ "type": "zone.join_request", "identity_token": "vlt_...", "location": { "lat": 40.7, "lng": -74.0 } }

// Zone → Vehicle
{ "type": "zone.join_accepted", "zone_id": "zne_...", "membership_token": "mbr_...", "stream_endpoints": [...] }

// Vehicle → Zone (telemetry stream)
{ "type": "zone.telemetry", "membership_token": "mbr_...", "streams": { "vehicle.speed": {...}, "vehicle.heading": {...} } }

// Zone → Vehicle (intelligence)
{ "type": "zone.intelligence", "route": {...}, "hazard_alerts": [...], "flow_instructions": [...] }

MNE Discovery API

GET /v1/mne/zones?lat={lat}&lng={lng}&radius_km={radius}
Authorization: Bearer {vital_api_key}

Response:
{ "zones": [{ "zone_id": "zne_...", "name": "Zone", "region": "...", "capabilities": [...] }] }

Zone is live and unified

Zone v1.0.0 has been published across DOSFI, MeshInfer, and MeshNativeExchange with full constitutional foundation — manifest, release, consent record, and audit trail. All 9 mesh nodes are synced with marketplace visibility and cross-system identity. Vital (DIU) compute settlement is enabled for all contributing nodes.

Constitutional ✓Runtime ✓Marketplace ✓Vital-settled ✓Governed ✓UT-compliant ✓