Sense → Verify → Push. The full pipeline, one page.
Three endpoints, three stages, the same verified-delta bundle an OEM map compiler ingests and a procurement lead reads at audit time. Each stage below names its inbound feeds, its outbound artifact, and the API + dashboard surface it touches.
Sense
A swarm of agents continuously pulls traffic, fleet telematics, and roadwork feeds as territory-attributed batches. Each accepted item is schema-versioned, receipt-backed, and stays EU-resident from the first byte.
- Live traffic anomaly feeds
- Fleet telematics turn counts
- Roadwork authority feeds
- Probe-quality normalisation
- Observation rows per RoadSegment
- Updated segment confidence + receipt status
- EU-resident ingest trail
Verify
The agent swarm flags drifted segments and cross-checks each flag against a second independent evidence class — a patch only leaves this step on a two-of-three vote. When a fleet partner changes, a recompute side-loop runs via POST /api/recompute to refresh route weights.
- Observations from Sense
- Cross-source evidence agreement
- Partner fleet route hints
- Drift flags with provenance log
- Fleet-specific route recompute
- Two-of-three vote gate
Push
Verified deltas leave as HMAC-SHA256-signed bundles, newest-first, owner-scoped, and tied to the ingest batch + recompute that produced them. A tampered patch fails verification and never reaches the ECU uploader; the audit trail is readable from /admin/audit.
- Verified deltas from Verify
- Owner / partner scope key
- PATCH_HMAC_SECRET
- Audit-traceable patch bundle
- Per-patch HMAC signature
- Compliance-readable provenance log
Tell us your fleet size, your incumbent telematics provider and the OEM you ship for. An engineer reads every intake and replies within one EU business day — usually with a worked integration plan for the three stages above.
Open the intake form