# 1. Why Hashpath?

[README](../README.md) | Next: [2. What a Hashpath is](02-WHAT-IS-A-HASHPATH.md)

---

Getting directions is solved.

Giving directions still sucks.

Map apps are good at routing. They can get a person near a destination. But real-world arrival often depends on details the map does not know:

- which gate is open
- which entrance is actually used
- where to park
- which door is unlocked
- which stairwell or elevator matters
- where the rideshare pickup point is
- which dock receives deliveries
- whether a code is needed
- what to do after hours
- where to go if GPS drifts
- what fallback route works when the obvious route fails

Hashpath exists for the gap between “the map says you arrived” and “you are actually at the right door, desk, dock, room, or handoff point.”

## The basic problem

Directions are often procedural.

```text
Turn into the second driveway.
Ignore the front office.
Go around the right side.
Park by the red fence.
Use the side stairs.
Text when you are at the blue door.
```

That is not merely a point. It is a sequence.

Hashpath gives that sequence a compact, structured, shareable form.

---

[README](../README.md) | Next: [2. What a Hashpath is](02-WHAT-IS-A-HASHPATH.md)