Location prompts: review the map and gate dispatch effects

Last updated: 4 Oct 202611 min read

tutorial

A route can pass arithmetic checks while its map points to the wrong entrance or omits a restricted road. The release packet should include ordered stop IDs, verified point identities, leg estimates, appointment windows, and a rendered map for human review. The map is a view of the route data, not proof that the points were correct. Before dispatching a change, recheck job status and technician availability; a completed or cancelled job must not remain in an active route. Sending the plan to a technician is an external effect with a recipient and receipt. If an update times out, reconcile the dispatch state before retrying.

Operational case

Quartz's plan for T-8 passes the three window calculations. The map preview reveals that J-52's marker sits at a loading dock closed to service vehicles, although the street address matches. The dispatcher substitutes the verified service entrance, refreshes affected travel legs, and reruns the feasibility check. Only after reviewing the updated route and the technician recipient does the user approve dispatch. A timeout after send triggers a receipt lookup; the assistant does not issue a second route simply because it cannot see the first response.

Review: ordered job IDs, entrance points, windows, leg IDs.
Map defect: J-52 marker at closed dock -> correct point.
Refresh changed legs and recompute arrivals.
Before send: job status and T-8 availability rechecked.
Send timeout: query dispatch receipt before retry.

Performance and operating cost

A map review adds a fixed human inspection plus O(S) stop checks for S route points. Recomputing only legs adjacent to a corrected stop is cheaper than rebuilding every candidate route, though global optimization may still be warranted if the correction changes feasibility. Receipt checks are O(1) average in a keyed store. The extra gates reduce wrong-address dispatches and duplicate technician instructions, both costlier than a short review.

Common Mistakes

Do not treat a rendered map as validation of the original point identities.
Do not send a route that still contains a cancelled job.
Do not resend after an ambiguous dispatch timeout without checking the receipt.

Connected lessons

prompt engineering

location dispatch