This is a working prototype, not a live product, and the difference is on screen rather than in the small print. Here is exactly which half is which.
This page what is real here, and what is not
“The risk detection is real — it runs against live news right now. The shipments are synthetic, so I can show you a disruption on demand instead of waiting for one.”
The injected strike uses the same event format as a live one, so it runs through the real pipeline rather than around it. The TMS link is the same idea in reverse: one door to the book, every decision written back onto the record it came from, but no TMS contacted and nothing written. A demo, not a live product — the wall between the two is integration and trust, and this connector stops at it.
Modelled end user
Head of Operations at a mid-size forwarder
DACH or Benelux, running the North Range corridors. Big enough that a Hamburg strike touches several bookings at once; too small for the enterprise risk platforms, which stop at the alert anyway.
The job it removes
Re-keying the consequences, one booking at a time
Watching is narrower than the problem and reacting is slower than the problem. The plank that eats the day is the second one: typing each decision — and each quote, booking, document and invoice the inbox brings — into the system of record by hand.
Each of these is a decision, not a gap — and saying so is cheaper than being found out.
No live TMS connection
Working through the TMS is the design; the far end is not built. No vendor, no credential, no endpoint, and nothing is ever written.
Nothing is sent
No email library and no transport of any kind is imported anywhere in the app. A test parses every file and fails the build if one appears.
No route optimisation
Routes are pre-authored candidates. The agent chooses among them and justifies the choice; it does not compute them.
No accuracy figures
Nothing here has been measured against real freight, so no percentage is claimed anywhere on this site. An invented number is the one thing this project refuses to produce.
No scheduler
Button-triggered. For a demo, the magic has to happen on screen, on command — not in a background job nobody can see.
No database
JSON files and memory. There is nothing to install and nothing to migrate.
No mailbox connected
The everyday desk works a synthetic morning of mail. No inbox is read and no Outlook or Gmail account is reached — the same wall as the TMS, on the other side of the desk.
No retraining
When you correct an agent, the correction becomes a lesson you can read, date and delete. No model weights change, and a lesson that would undo an earlier correction is refused.
Seen enough to want a look at your own lanes?
Half an hour, your corridors, your disruption.