A dispatch console that refuses

One self-contained HTML file — no build, no server, no persistence. It is dressed as the working product on purpose: an operator opening it should recognise it as software, not as an argument about software.

The question: can a delivery spreadsheet be replaced by real transactional state? Not “does a dispatch screen look like this” — that one is cheap. The doubt worth answering is whether the guards, the attempt count, the cash reconciliation and the audit trail actually hold when somebody tries to do the wrong thing.

So this set is one prototype, built deep, rather than four competing directions. The wedding and school sets ask a client which shape they prefer. This one asks whether the hard part works, and the only honest way to show that is to let you try to break it.

How to drive it. Open an order and the panel on the right becomes its controls. Actions that are not allowed are not on screen — they sit in a list underneath with the rule that blocked each one. The Demo drawer along the bottom holds five guided scenarios, the spreadsheet this replaces, and a live list of what it guarantees; it also resets the day.

1. 01 Orders consolePrototype Hatid Logistics · Metro Manila last-mile · 40–60 drops a day

   A working console: orders board, driver load, activity log. Eight orders move through named stages — assign, load, send out, deliver, fail, reschedule, cancel — and the console refuses out loud, naming the rule rather than going quiet. The spreadsheet it replaces, with its four live defects, sits in the demo drawer: four spellings of “delivered”, one parcel on two drivers, a cancelled order still eating a slot, and an attempt history that gets typed over.

   Doubt

   Can they replace a spreadsheet with real transactional state?

   Model

   Every parcel moves through eight named stages, with the rules enforced in one place

   Proof

   Seven promises, re-checked against the records after every action