Part 1 — Korido: the product and its world

Before a single tracker signal can mean anything, you need the shape of the thing it feeds. This part is that orientation. It answers what Korido is and the problem it exists to solve, who works inside it, how a reading travels from a truck on the Douala–N'Djamena corridor to the map an owner reads and the alert on their phone, and the shared vocabulary every later chapter leans on.

Read it once, top to bottom, and the rest of the book has somewhere to land.

• What is Korido — the corridor and its two-thousand kilometres of blind spots, the four roles (owner, driver, admin, viewer), the surfaces each audience meets, and the one principle everything rests on: the hardware tracker on the truck is the single source of truth for where that truck is — never the driver's phone.
• System at a glance — one signal followed end to end, from the tracker through Flespi, the API Worker, the queue, and the Engine Worker to the map and the alert; then the four data planes — reference, plan, observed, and intelligence — that organise everything Korido stores and computes.
• Vocabulary — the glossary the whole handbook shares: waypoint, corridor, mission, trip, stop, gap, fix, heartbeat, Route Guard, and the rest, each defined once in plain language.

Everything in this book happens inside one tenant — a single trucking business, isolated from every other. That word, and every other one the later parts assume you already know, is defined here first.

How it connects

• Next: Part 2 — Telemetry follows the life of a single signal from the tracker to the live vehicle state.
• The surfaces introduced here get full chapters of their own, starting with the fleet app; the tenancy and isolation model is in Tenancy and security.