Motion & Geofence Engine

This is the physical product surface for the capability described on the customer journey map as motion_geofence_engine and motion_intel_api. One server evaluates GPS against corridor polylines, merged port and border anchors, intel polygons, and prior journey state — the same contract Dispatch uses for trip-level Geofence Compliance.

Open journey map — Motion live lab Open Geofence module (full platform) Dispatch command center GET integration-status (JSON)
1 · Customer journey map Capability matrix + staff narrative. Capability IDs tie this hub to documentation you already maintain.
/customer-journey → #motionLiveLab
2 · HTTP API Policy bundle on GET; authenticated evaluate on POST (JWT, admin key in private dev, or MOTION_EVALUATE_ALLOW_UNAUTH where appropriate).
/api/motion-intelligence
3 · Dispatch UI Trip detail “Geofence Compliance” card; optional live enrich via WajeehMotionIntel.evaluate when trip has motion binding + coordinates.
/dispatch
4 · Server engine Haversine corridor distance, cargo envelopes, touchpoints, Hazalyze overlays — implemented in repo library consumed by the API route.
api/_lib/motion-corridor-engine.js

Live evaluate (same POST as journey map)

Uses a separate browser storage key from the journey page so two tabs do not overwrite journey memory unless you use the same trip ID and clear state intentionally.

Ready. Open from your deployment origin so /api/motion-intelligence resolves.