Manifests and evidence
The manifest response contains manifests, unplanned_movements, technical evidence, and notices.
Driver manifests
Each manifest identifies a driver and an ordered list of timed activities:
drivepickupdeliverybreakwaityard_workservicehold
Activities refer back to movement, booking, Nugget, lorry, and location identifiers. Drive activities include origin and destination locations; pickup and delivery activities include the relevant movement and Nuggets.
Booking-check status
| Status | Meaning |
|---|---|
feasible | The bounded check found a valid manifest containing the proposed movement legs. |
infeasible_proven | A hard contradiction proves the request cannot fit as supplied. |
unknown | The bounded check found no plan and proved no contradiction. This is not a rejection. |
A booking check is the fast capacity path. A full multi-day fleet replan remains a batch operation.
Evidence and notices
Responses identify the applied planning_policy, vehicle_profile, traffic_model, road provider, map label, and matrix digest. Manifest responses also identify the planner backend, elapsed planning time, independent validation result, and any fallback code.
Notices disclose provisional inputs, such as an unconfirmed HGV profile or missing current Fleet Check allowances. They are planning qualifications, not customer-facing decisions.