The fleet that learns where. Spatial digital twins, federated route learning, and GNN optimization for geo-distributed intelligence.
Part of the [&] Protocol stack · Ecosystem overview · Three-protocol stack · Stack status
Welcome to the documentation hub for GeoFleetic — the spatial intelligence layer of the [&] Protocol ecosystem. GeoFleetic provides geo-distributed fleet tracking, federated route learning, and GNN-based route optimization — all running on the BEAM for fault tolerance and real-time concurrency.
GeoFleetic is the &space primitive provider, exposing &space.fleet, &space.route, and &space.geofence capability contracts to the rest of the [&] stack.
Fleet management systems today are centralized, batch-oriented, and privacy-hostile. A logistics company with 10,000 vehicles streams all GPS data to a cloud API, which returns routes computed on stale models. The fleet learns nothing from yesterday's deliveries. Privacy regulations (GDPR, CCPA) make centralizing raw location data increasingly untenable. And when the cloud API goes down, the fleet goes blind.
GeoFleetic provides spatial intelligence that:
Lives at the edge — each vehicle reasons locally with sub-second latency
Learns continually — routes improve from every delivery, not quarterly retraining
Preserves privacy — shares model updates, never raw trajectories
Tolerates partitions — vehicles operate offline and reconcile when reconnected
Composes with other intelligence — spatial context enriches upstream reasoning
Homepages
Root Docs
GeoFleetic Docs
| Capability | Operations | Description |
|---|---|---|
&space.fleet | locate, enrich, capacity, route | Fleet tracking and spatial digital twins |
&space.route | route, optimize, explain | GNN-based route learning and optimization |
&space.geofence | contains, enter_exit, enrich | Dynamic geofence boundary evaluation |
Spatial digital twins — delta-CRDT-backed replicas that converge under partition
Federated learning — LoRA adapter deltas shared across fleet, raw GPS stays on-device
GNN route optimization — graph neural network continual learning for route quality
Multi-timescale memory — edge SQLite + sqlite-vec, fleet-level PostGIS + Tile38
MCP + A2A protocols — all capabilities exposed as MCP tools
| Component | Role | OTP Pattern |
|---|---|---|
| Fleet Tracker | Delta-CRDT spatial digital twins | GenServer per asset |
| Route Optimizer | GNN-based continual route learning | GenServer + Nx |
| Geofence Engine | Tile38-inspired boundary evaluation | Concurrent tasks |
| Federated Coordinator | LoRA delta aggregation, privacy budgets | GenServer |
| Fleet Dashboard | Maps, routes, geofences, capacity heatmaps | Phoenix LiveView |
| Product | Relationship |
|---|---|
| TickTickClock | Temporal intelligence — when + where = complete situational awareness |
| Graphonomous | Continual learning substrate for fleet knowledge |
| Delegatic | Governance enforcement for fleet operations |
| Layer | Technology |
|---|---|
| Language | Elixir 1.17+ |
| Framework | Phoenix 1.8+ |
| Database | PostgreSQL 16+ + PostGIS |
| Spatial Index | Tile38 (or equivalent) |
| Edge Storage | SQLite + sqlite-vec |
| ML | Bumblebee / Nx (GNN, LoRA) |
| Replication | Epoch-aware delta-CRDTs |
Spec: Technical Specification
[&] Protocol ecosystem: AmpersandBoxDesign/
[&] Ampersand Box Design — geofleetic.com