Handbook

Appearance

Vocabulary ​

What this chapter covers ​

This is the glossary the whole handbook leans on. Each term is defined once here, in a single paragraph, in plain language. Later chapters bold a term on first use and assume this page for the rest. The definitions are ordered alphabetically; the diagram below shows how the main terms relate as a signal becomes a journey.

The picture ​

Everything below happens inside one tenant — one trucking business, isolated from every other.

Glossary ​

Anomaly — a disruptive incident on a corridor that blocks or badly slows forward progress: a road closure, a blockade, a major backup. Korido captures anomalies (corridor_anomalies) as cross-fleet intelligence, each with an expected time cost, and when an anomaly blocks progress it turns an affected mission's ETA confidence to blocked rather than pretending the truck will arrive on time.

Client — the operator's customer: the shipper or consignee a mission is run for (clients). A client record is deliberately lean — a name and a contact — but it carries the operational weight of saved client locations, a default corridor and driving policy that quick-assign reads, and the tracking links shared with that customer. A client is soft-deleted, never erased, so past missions that named it stay readable.

Client location — a saved association between a client and a map waypoint in a role — pickup, delivery, or both (client_locations) — optionally labelled. Client locations are what let picking a client in the mission wizard pre-fill the route's origin and destination, so a routine run starts with its endpoints already chosen.

Convoy — a group of missions dispatched to travel together, several trucks running the same corridor at once for safety or coordination. One convoys row ties the missions together as a single dispatch and reporting unit; the quick-assign flow can create N missions and one convoy in a single pass.

Corridor — a named, ordered path of waypoints that defines a reusable route, such as Douala to N'Djamena. A corridor is the sequence of places, and each leg resolves to a road segment when needed. Corridors are curated once and attached to missions, templates, and clients, so a route worth running is a route worth naming.

Deviation — an excursion off the agreed route. When a truck leaves its mission's Route Guard region, Korido opens a deviation (corridor_deviations) and records when it left, when it returned, how far and how long it strayed, and why the excursion closed. Deviations are how off-route behaviour becomes a measurable, alertable fact.

Document — a photo of paperwork a run generates — a customs form, a signed delivery note, a fuel receipt, a vehicle paper (documents) — captured by a driver on the phone, attached to the mission and truck it belongs to, and worked by an owner in a review center. A document moves through a small status set as it is reviewed — Validé, À corriger, or Rejeté — and a correction or rejection sends the driver a directed retake request.

Driver — a person record that is both a login identity and a mission assignee: a tenant user with the driver role, keyed by a phone number that is their one-time-code login to the driver app. A driver record is the prerequisite for both dispatching — every mission names a driver — and driver-app access, and deactivating one preserves the missions it ran.

Fix — a position reading that carries real coordinates: the truck's actual location at a moment in time. A reading with no coordinates is a no-fix reading, delivered as a status frame. All geometry — trips, distance, deviations, arrivals — is built only from fixes; no-fix readings still feed liveness, ignition, and fuel, but never place the truck on the map.

Gap — a window in which Korido stops receiving usable positions and the truck goes dark. A gap opens once silence passes a threshold — 600 seconds while the truck was moving, 1800 seconds while it was stationary — and closes when signal returns. It is then classified by likely cause (data_gaps): signal_loss, power_off, stationary_offline, tampering_suspect, or unknown.

Heartbeat — any contact from the tracker at all — a fix, a status frame, any telemetry — that proves the hardware is alive. The heartbeat clock answers "when did we last hear from this device?", which is distinct from the last position fix. When a device's heartbeat falls silent past the tenant's threshold (default 30 minutes), Korido raises the offline alert.

Hotspot — a place where stops and events recur across the fleet: a customs post, a weighbridge, a chronic bottleneck. Korido clusters observed stops and events across tenants into hotspots (route_hotspots), each carrying its own statistics and an expected time cost, so a known slow place is anticipated on the next run rather than rediscovered every time.

Mission — one planned journey for one vehicle: a truck and driver assigned to carry a load along a corridor from origin to destination. A mission moves through an eight-state lifecycle — created, assigned, en route to origin, active, paused, arrived, completed, cancelled — carries its ordered waypoints, its Route Guard region, its resolved rule set, and its live ETA, and only one mission is active per vehicle at a time.

Mission template — a saved preset that turns a common run into a one-tap dispatch. A template carries the corridor and direction, the preferred vehicle, driver, and trailer, cargo defaults, and the rule set — everything a mission needs — and ranks itself by how often it is used so the right template surfaces first.

Quality flag — the label the engine attaches to a fix that records how far to trust it: accepted, spike, jitter, or late. It lets Korido keep every reading for the record while deciding which ones may move the truck, alter the route, or fire an alert. No-fix readings carry no quality flag, because they are never classified as positions.

Road segment — the curated geometry of one road between two waypoints: a centre-line and a buffered region an admin has drawn once (road_segments). Because one road (Douala to Yaoundé) is shared by many corridors, its geometry is stored once and reused; a reverse row exists only where a road genuinely diverges by direction of travel. Road segments are the region source for Route Guard and the geometric baseline for per-segment analytics.

Route Guard — Korido's corridor-monitoring feature and the name it wears in every user-facing surface. Route Guard holds each active mission's route as a region and continuously checks the truck's trusted position against it, opening a deviation when the truck strays and clearing it when it returns. It is what turns "stay on the agreed road" into an enforced, alertable promise.

Rule set — a named driving policy attachable to a mission (rule_sets): maximum speed and tolerance, night-driving window and mode, hours-of-service limits, authorized fuel stations, and prohibited stops. Rule sets resolve by inheritance — mission, then template, then client, then corridor, then tenant default — and apply live, so editing a policy takes effect on missions already under way. Their enforcement producers emit vehicle events for speeding, night-driving violations, unauthorized refuelling, and prohibited stops.

Segment traversal — one truck's single observed crossing of one road segment: the atomic fact "this vehicle drove this stretch, this time" (segment_traversals). Each traversal records transit and driving time, distance, speed, stops, gaps, and idle, denormalized with the driver, vehicle, cargo, client, and calendar context of the run. Segment traversals are the analytics spine — the rows that, in aggregate, answer why leg four is always slow or which driver clears customs fastest.

Slowdown zone — a stretch of corridor where trucks reliably lose speed: a rough patch, a long climb, a congested approach. Korido detects raw slow events and clusters them across the fleet into slowdown zones (slowdown_zones), each with an expected time cost, so recurring slowness is modelled rather than mistaken for a one-off.

Status frame — a tracker message that carries telemetry but no coordinates: a voltage heartbeat, an ignition change, a fuel reading sent while the truck is parked. Status frames are kept as no-fix position rows; they keep a vehicle's live tiles fresh — ignition, battery, signal, voltage — advance liveness, and feed fuel and tamper detection, without ever being read as a location. This is why a parked truck streaming status frames still shows live status instead of freezing at its last fix.

Stop — an interval during which a truck is parked, reconstructed by the engine and classified by why it stopped. The classification is one of seventeen exhaustive categories, including authorized_waypoint, border_crossing, weighbridge, customs, toll_gate, fuel_station, mandatory_rest, breakdown, roadblock, and clandestine. Classification is what turns "stationary for three hours" into "three hours at the border."

Tenant — one trucking business on the platform: its own fleet, drivers, clients, missions, and history, isolated from every other business. Isolation is enforced on every read — each tenant-scoped record carries a tenant identifier and each query filters on it — so no read ever crosses from one business's data into another's.

Tracking link — a scoped, expiring URL an owner shares so a customer can follow one delivery on the tracking portal (tracking_links). Mission, client, and convoy links are gated by the last four digits of the recipient's phone; ad-hoc links ask for the full phone because they have no mission context. A link covers one mission or several, carries a lifetime of 7, 14, or 20 days (capped at 20), and can be extended or revoked at any time — revoking rotates its secret so every gate pass already issued stops working.

Trip — a continuous driving window: the truck moving from when it sets off until it next parks. Trips carry distance, speed, and idle summaries and the place labels of where they began and ended, and they are the backbone of the vehicle diary — the human-readable story of a vehicle's day, assembled from raw positions.

Waypoint — a named, geofenced point on the map: a port, a depot, a customs post, a border, a fuel station. Waypoints can nest, such as a port inside a city, and their geofences are what let Korido detect that a truck has arrived somewhere meaningful. They are the nodes from which corridors, missions, and visits are built.

Waypoint visit — the record of a truck entering and leaving a waypoint's geofence: arrival time, departure time, and dwell (waypoint_visits). Waypoint visits are how Korido measures time spent at named places — how long at customs, how long loading at the depot — and how it marks the boundaries between the segments of a journey.

How it connects ​