Lanes freight exceptions
World clock Tue 18:00:00 UTC held · 120×

Known gaps

What Lanes does not handle, and what a pilot needs for each.

Known gaps

This page lists what Lanes does not handle, and what its numbers can and cannot show. Read it before you trust a figure in the README.

The data is synthetic

Every port, carrier, shipment, incident and person is generated from a seed (python -m lanes.world.generate --seed 23 --out data/lanes-seed23.duckdb). Nothing comes from a real forwarder, carrier, terminal or customs system.

What that gives:

What it cannot show:

The world does not react to the operator

The world is generated once, with its whole future. When the operator acts, the tables it touches change (an appointment, a request, a hold, a corrected number), but what follows is not simulated again:

So the numbers measure detection and the first decision, not what the operator's actions would have saved. The ledger shows the money at stake as a projection, never as money saved.

Incidents at the end of the window

Some problems cannot be seen until a grace period has passed: an ETA slip needs four hours without an update, a roll three, a reefer run four readings (nine hours), a customs hold thirty minutes. An incident that starts at 17:00 on the replayed Tuesday cannot be detected by 18:00, and counts against recall.

Detector limits

What a pilot needs first