VERIFIED USERS · AUTOMATIC MOTION · PERSISTENT ROUTES
Register availability or need on a common system without announcing where you are.
THE SOCIAL PROBLEM
Every morning, empty seats pass people who need to travel along nearly the same corridor. The useful fact is not that somebody can be dispatched right now; it is that a verified neighbor reliably goes from X to Y on Tuesdays and Thursdays and may be willing to cooperate. That durable overlap is normally invisible unless the two people already know one another.
The cost of that invisibility is not evenly distributed. The Bureau of Transportation Statistics reports that Americans with travel-limiting disabilities make fewer daily trips, are less likely to have a vehicle, and often compensate by asking others for rides or limiting when they travel. A missed route match can therefore become a missed shift, appointment, class, or relationship.
Routes is a mobile social network for verified users. It records motion data automatically and, after the same trip occurs several times, asks whether it is a regular route. The user can register availability or need as “I am traveling from X to Y”, letting the service compare persistent routes without announcing anyone’s live location.
ONE CORRIDOR · TWO TIMELINES
Sam drives from the north edge of town to the hospital district four mornings a week. Three streets away, Elena stops accepting an early physical-therapy appointment because the bus connection is unreliable and a commercial ride twice a week would consume too much of her fixed income. Sam would gladly discuss a regular neighborly arrangement, but neither person knows the overlap exists. The empty seat and the unmet need repeat for months.
After several trips, Sam’s phone asks whether this is a regular X-to-Y route. Elena registers recurring need along the same corridor and time window. Routes reveals a compatible verified person—not a moving dot—and the two choose an introduction. They work out their own arrangement. No ride is requested, no driver is dispatched, and no fare passes through the network.
THE ROUTE LOOP
WHAT PEOPLE CAN DO
Routes is deliberately social infrastructure rather than a transport transaction. It makes compatible routines discoverable, then leaves verified people room to form a rideshare, a recurring favor, a walking group, or another holistic arrangement that a fare-and-dispatch product would never recognize.
Two coworkers discover that their flexible morning corridors overlap four days a week.
A verified neighbor already passing a clinic can discuss recurring assistance with another household.
Families on the same school corridor form a recurring walking or bike group.
A nonprofit sees an opt-in cluster of unmet corridor needs without receiving household identities.
PRODUCT BOUNDARY
The absence of a transaction is functional. A request button would recast every available neighbor as an on-demand driver; payment would force the network to price favors and relationships it was meant only to reveal.
NO live public location
NO “request ride” button
NO fare, tip, or payment
THE BUSINESS MODEL
Public planning depends on origin, destination, time, and purpose patterns; the Federal Highway Administration’s National Household Travel Survey exists to collect exactly that broad picture. Routes could produce a more continuous view of recurring corridors while financing the social network that makes those corridors useful to individuals.
The network collects the repeated movement information needed to infer persistent routes.
Individual journeys are grouped into traffic information rather than exposed as live user locations.
Traffic-information-using entities and planning entities buy the bundled picture of recurring movement.
TRUST ARCHITECTURE