Part 5 — Missions: the work trucks do on the road

Part 4 handed us the map. This part is the job that runs on it. A mission is Korido's unit of operational accountability: one truck, one driver, one planned route, one set of pickup and delivery milestones, one audit trail — the thread that ties a fleet's assets, its plan, its live tracking, and its analytics together.

To keep the abstractions concrete, the whole part follows one run: a tanker loading fuel at the Douala port, bound for N'Djamena, roughly 2,000 km across two countries. We meet it first as assets and the driver who runs them, learn who the haul is for, then plan its route, watch it depart and arrive, govern how it may drive, estimate when it lands, cut its journey into the measured legs that teach the next mission, and file the paperwork it produces along the way.

• Fleet assets — the things a mission is carried by and the person who runs it: the vehicle that streams telemetry, the trailer that often holds the cargo, the tracker-and-SIM stack wired into the cab, and the driver assigned to the haul. How each is registered, linked, swapped, and marked available or off the road.
• Clients — who the work is for: the customer record, its saved pickup and delivery locations, the default corridor and driving policy it lends to a mission, and the tracking links shared with it.
• The mission lifecycle — the eight states a mission moves through, how it advances on its own as the truck crosses geofences, how it pauses and resumes, how a mistaken start is unwound, and the rule that a vehicle can be on only one live mission at a time.
• Creating missions — dispatching in a tap: quick-assign from a client's templates or from a pickup-and-delivery pair, convoy dispatch across several trucks, and what a mission write actually commits before external routing enriches it.
• Driving rules — the policy a mission runs under: speed, night driving, hours of service, and authorized-refuel and prohibited-stop places. Why this policy is applied live while the route geometry stays frozen.
• Progression and ETA — how Korido answers "when will it arrive?" without ever promising — a continuously re-estimated arrival built from per-segment history, known frictions, and rest modelling, each estimate carrying its own confidence.
• Segments and traversals — where a journey becomes comparable: waypoint boundaries cut the run into measurable legs, each frozen with its facts, its context dimensions, and the prediction made beforehand — the raw material for Part 6.
• Documents — the paperwork a run generates: a driver captures customs forms, delivery notes, and fuel receipts on the phone, they attach to the mission and truck, and an owner works them in a review center with a retake loop back to the driver.

By the time our tanker reaches N'Djamena it has left behind a full, comparable record of the run — every leg timed, every stop and deviation attributed, every litre accounted for, every document captured and reviewed. That record is where Part 6 begins: the fleet intelligence that turns one mission's facts into what a whole fleet can learn.