Planning method
Route evidence is dated, not live navigation
Asmaliana treats travel time as evidence with a source, scope, and expiry—not as a promise that a road will remain clear. This guide explains how to read a route result before relying on it in a one-day plan.
A route edge is a reviewed input
The verified release uses a rights-cleared FOSSGIS/OSRM driving snapshot for the published place pairs. The current matrix contains 2,652 directed edges over 52 reviewed places and records its retrieval time, source hash, and validity deadline.
The snapshot is one input to a deterministic check. It is not a venue confirmation, and it does not expand the set of places that the current dataset covers.
Intervals are intentionally conservative
A provider duration is normalised into a minimum and an upper bound. The itinerary checker uses the upper bound for hard timing checks and applies any declared buffer. It never converts a straight-line distance into a travel time.
- A valid edge can establish a bounded transfer assumption.
- An expired edge is stale and cannot establish a route duration.
- A user-supplied estimate remains an explicit assumption, not provider evidence.
If the time between two stops is shorter than the reviewed upper bound, the result can be an established timing conflict. If the edge is missing or expired, the result is needs_verification; the service does not silently substitute a guess.
What a route result cannot establish
The snapshot does not know live traffic, queues, closures, road incidents, parking, turn-by-turn instructions, weather safety, or whether a venue will admit a traveller. A route that fits the snapshot can still require direct confirmation.
The route source carries OpenStreetMap/ODbL attribution and a public-use record. A cache hit preserves the original retrieval and expiry metadata; it does not make an old edge fresh.
How to use the result
Read the route state and validity deadline from the status metadata, then inspect the itinerary response’s checked dimensions, assumptions, blocking unknowns, and unchecked dimensions. Treat feasible as “all declared constraints passed inside the stated evidence scope,” not as a navigation or travel guarantee.