Our own rideshare platform: a rider app, a driver app and a dispatch console on one harmonised positioning service and one map — when a driver accepts, the rider watches the driver's true position move, from the same single record the driver and dispatch see. Tabs for Transportation, Food delivery, Market / Business, Communication and Airlines, on one account.
Windows — one file. Run it: it downloads the official Python engine once (fingerprint-checked), installs the platform, leaves a “RideShare Platform” launcher on the Desktop and opens the three apps.
⬇ RideShare-Setup.exe — Windows (495 KB)Linux — one file. Save it, then run sh rideshare-linux-setup: it installs into
~/RideShare, leaves a Desktop icon, starts the platform and opens the apps.
Android — the rider and driver apps. They open the platform running on your computer:
install the platform first (above), then in the app type your computer's network address, for example
http://192.168.1.20:8791, and press Connect.
Advanced: rideshare-platform.zip (228 KB) is the plain platform folder the setups install — the exact bytes the test gate passed.
First steps once it opens: create a driver account in the Driver app (it starts unsubscribed, on purpose);
log into the Console as the seeded administrator (admin@rideshare.local, password
ChangeMe!2026 — change it before any real use) and activate the driver's subscription;
the driver can now go online. Create a rider account, tap the map twice (pickup, then destination) and request.
In the Driver app, switch Simulated driving on and accept the ride — then watch the car move on the
rider's map, on the driver's map and on the console map: one car, one position, three screens.
Before this page existed, the platform passed an automated gate in a fresh environment: agent riders, agent drivers and an agent administrator performed every function through the real interfaces. 70 / 70 checks passed — 0 failed
| What was exercised | Result |
|---|---|
| Position truth — during 3 full live trips, the driver position shown to the rider, to the driver and to dispatch was sampled and compared version-by-version | 252 samples, 0 divergences (4 samples skipped where a simulation tick landed mid-fetch) |
| Full trip journeys: request → nearest-driver offer → accept → drive to pickup → trip → complete → fare → ratings both ways | 3 / 3 completed; fares computed from real routed distance (1.76 km test route) |
| Subscription gate: unsubscribed driver tries to go online; admin activates; suspension mid-test | Refused with SUBSCRIPTION_REQUIRED · admitted once subscribed · suspension forced the driver offline |
| Role powers: rider using driver powers, driver requesting rides, stranger reading a trip, rider doing restaurant steps | Every forbidden action refused (403) |
| Decline path: offered driver declines | Trip re-offered to the other driver, never back to the decliner |
| Food delivery tab: order → restaurant accepts → ready → courier claims → pickup → delivered | Closed end to end; server computed the total |
| Market tab: listing → order | Placed at listing price × quantity |
| Communication tab: rider ⇄ driver messages on our own platform (no third-party service inside) | Two-way thread proven |
| Airlines tab: search over 4,571 airports with IATA codes + 81 airline codes | Results are DEMO-marked; booking a non-DEMO flight is refused by the server |
| Safety: SOS from the app | Landed in the dispatch safety view |
| Security: anonymous and tampered-token calls to the position feed; credential storage | Refused (401); passwords stored PBKDF2-hashed; session tokens stored hashed |
| Failure path: ride requested with no driver online | Answered plainly as NO_DRIVERS — nothing failed silently |
| Linux setup file installed into a clean home folder and launched | Installed, Desktop icon created, installed copy answered health checks |
| Windows setup file run under Wine (compatibility layer) | Executed, stated its internet requirement, attempted the verified download, and on failure left nothing half-installed. A run on a real Windows machine is still owed — see open items |
A full sourced inventory was compiled from the platforms' public pages before building. The baseline both big platforms share — upfront fare, live tracking, trip sharing, mutual ratings, safety toolkits — is matched here in v0 form where it counts for a first working version: full trip lifecycle, live shared map, ratings both ways, SOS to dispatch, admin console. Empower proves the owner's business model in the real market: drivers pay a subscription (publicly listed plans run from about $49.99 a month tiered by earnings up to $449.99 unlimited in Washington DC) and keep their fares, paying no per-trip commission. This platform's gate implements exactly that model.
Gaps we deliberately close: one verifiable positioning source shared by both apps (no platform publishes position truth); rides + food + market + messaging + airlines on one account; a subscription that is published and visible to the driver in the app, not hidden by city and tier.
| Item | Status |
|---|---|
| iPhone / iPad native app | Web-app form works now Open the platform address in Safari — rider, driver and console are web apps and run there today. A native App Store app is gated on Apple's developer process; it is not faked here. |
| Windows setup on a real Windows machine | Owed Proven under Wine up to the download step (which correctly aborted in that sandbox). First run on the owner's Windows laptop completes the proof; the platform bytes it installs are the same bytes the Linux install and the 70-check gate proved. |
| Android apps on a real device | Owed Built and signature-verified here; not yet run on the owner's Samsung devices. Google Play Protect may question sideloaded apps (the same known item as our other apps). |
| Real payments (fares, subscriptions, tickets) | Not in v0 No card data exists anywhere in v0. The payment-card control family binds the moment real charging switches on, through a processor's hosted payment path — a gated v1 build. |
| Real flight inventory | DEMO only Flight results are schedule-shaped demonstration data built from the open IATA code sets, marked DEMO everywhere. Live inventory is a licensed data product (IATA and partners) for a later, funded step. |
| Encryption in transit | Local test form v0 runs on your own machine/network over plain local HTTP. Before any public deployment, HTTPS everywhere is a hard gate, per our standing rule. |
| Restaurant accounts | Worked from the console in v0 A dedicated restaurant role is a v1 item. |
Map: a real street network (3,532 junctions, 3,732 road segments, Montgomery Village, Maryland) from OpenStreetMap contributors, ODbL (Open Database License) — attribution is printed on every map in the apps. Airports: OurAirports, public domain — 4,571 airports carrying IATA (International Air Transport Association) codes. Airline codes: IATA-assigned identifiers compiled from public sources; no IATA-licensed data product was used, and the licensed products are named as licensed in the project's control map. The platform code is ours, built on established public cryptography only.
File fingerprints (MD5): RideShare-Setup.exe 01555815b6d76f39727c24f10912b1f4 ·
rideshare-linux-setup d42f9db550b991a9945a6c083a797aef ·
rideshare-rider.apk e8c1df93affb8a3999ea744a20ed78fa ·
rideshare-driver.apk 5a59acfe3e8439e16494d0ec808d4fb5 ·
rideshare-platform.zip 052e135420a8eda025607bb67f7772f6