Last-Mile Delivery

Delivery operations run at speed and at volume. A dispatcher who asks a model for a route note is not thinking about what the prompt contains. The same checks apply to every one of those requests.

Dispatch teams ask for a route order, a delay explanation or a note to a customer. The starter reads that request and the reply. It cannot assign a stop, message a courier or call a tool, so the dispatcher stays responsible for the plan.

Know what masking covers before you rely on it. The patterns hide operator and badge numbers, maintenance or on-call phone numbers, and shift, crew and duty roster references. Customer names, delivery addresses and consumer phone numbers are not in that set. Add patterns for them if couriers paste customer detail into prompts.

Two refusal lists guard the request. One ends anything that names a facility blueprint, a safety interlock or a control system password. The other carries built-in wording against explosives, weapons and attacks. Both compare words only, and neither can separate a threat from a report about one.

The reply gate expects 0.87 combined, 0.78 relevance and 0.80 accuracy, with the two counting equally. It also expects 120 characters and two sentences. A reply that falls short is refused instead of shown, and streamed replies skip the gate entirely.

ISO 27001, NIS2 and ISO 39001 sit behind the starter. Driver hours, road safety and dispatch rules stay in your own programs. Human review is present but unconfigured, so treat it as a control to enable. The audit step marks an evaluated request and never blocks it.