The confirmed location is the origin. Distance is the travel, pickup, or delivery burden, like moving freight from a facility to a destination.
FOOD DECISION PROBLEM
Choose what you should eat—solo or together.
A meal is a small logistics problem. One person or a group starts in a place, has tastes and hard constraints, chooses breakfast through late night, decides between quick service, sit-down, takeaway, or delivery, and needs one workable answer.
STEP 1 · CONFIRM THE ORIGIN
Where are you starting?
Search a place, use your current location, or click the map. Atlas Harbor will not rank restaurants until you confirm the origin because travel cost, pickup burden, and delivery feasibility depend on it.
Choose a point before continuing.
Click the map to move the origin. Map data follows the deployment’s configured tile provider.
STEP 2 · DEFINE THE DECISION
What kind of meal are you solving?
THE LOGISTICS CONNECTION
A meal decision uses the same structure as a network decision.
Hours, meal time, service style, distance, price ceilings, dislikes, and dietary needs define which options are feasible.
A solo decision maximizes one diner’s fit. A shared decision protects the least-satisfied person before improving the average.
Map listings cannot prove delivery day, cold-chain handling, allergen controls, or raw-shellfish safety. Those become explicit verification tasks.
Rankings combine diner fit, breakfast-to-late-night availability, service mode, travel, evidence confidence, and freshness questions.
The output explains the fit, exposes tradeoffs, and identifies what to call or verify before ordering or leaving.