The arithmetic behind the grey
Waze's edge was never its UI — it is the live ping of hundreds of thousands of vehicles fused into one per-segment truth. Every Malaysian app has a better local product (toll economics, AES alerts, Malay addressing, flood awareness), but each crowd on its own is one to two orders of magnitude too thin. The result any driver can see: grey roads where the foreign incumbent renders colour.
The honesty gate that causes it is a single line of production code: a segment gets a traffic state only when enough samples exist in the window. It counts samples on the road, not samples per app — which is why this is arithmetic, and why pooling is the only honest fix.
Measured, not asserted
Before asking any partner or agency to join, we ran the exchange gate against the live production gateway with synthetic member crowds. The same road was grey for one thin crowd (3 samples, below the gate) and coloured the moment a second crowd pooled in (6 samples, state read back: fast, confidence 0.24). Four members mixing fast and slow blended honestly to medium and confidence rose to 0.40. Zero code changed — the gate was always counting total samples.
The coverage model says the same shape at network scale: one thin app alone colours under 1% of corridors; five pooled crowds lift most of the network to live. That is not a feature you can out-market.
“Malaysia already has the sensors; it has never had the glue. MyTIE is the open glue — it turns control-room CCTV, adaptive signals and every app's drivers into one Malaysian-owned live road state none of you can build alone.”
Built for the government, by design
The state has already picked this fight: the October 2026 civil-servant ban on Waze and the push toward the national TuJu app. But the structural fact remains — the app with the crowd was banned and the app without one was promoted, and a thin sovereign crowd is still thin. Meanwhile the country's real traffic-intelligence estate — KLCCC's AI signal control and KL digital twin, LLM's highway CCTV and TRAXX FM, operator control rooms, JPJ's AES network — is fixed-sensor, agency-siloed and video-based. None of it publishes open per-segment road flow.
MyTIE asks for no new hardware. It ingests agency feeds as authoritative indications the crowd verifies, exposes the paid-for ITS estate as data, and adds the mobile probe layer the country has never had — Malaysia-hosted, PDPA-by-design, aggregate-only, auditable open code. No trajectories, no identities: fields that look like them are rejected at the schema layer. It follows the GTFS precedent — the open transit-data commons the state adopted and every app got better.
Owned by all, held by none
The exchange is not anyone's product. A member council with one-member-one-voice owns the spec; the reference implementation and the canonical segment registry (OSM way + direction) live in a neutral open-source home with no founder veto; fused outputs carry a share-alike national-data-commons licence so no member can enclose the pool. Pull quality is a deterministic, auditable function of contribution, and any member can run its own instance and diff the output — neutrality is testable, not promised.
The protocol draft, the governance charter and the Stage-0 evidence are published on the product page. The ask today is small: a working session and a two-app pilot on defined KL corridors. If you are an agency, an app or a fleet, the contact page is open.