Eight parts, one shared road state
AnTIE is not a product you install — it is a piece of shared infrastructure a dozen competitors and several agencies use together. Here is every component, honestly tagged: what already runs in a production Malaysian navigation stack, what is specified, and what is still only proposed.
The exchange, part by part
Runs today means shipping in AnOmbak's live gateway; designed means specified against that running code; proposed / draft charter means we are naming it before it exists.
The segment registry
A national canonical road-segment identity — OpenStreetMap way + direction, open-licensed, versioned and diffable. Every member computes the same road graph, so fusion is deterministic and reproducible; the registry itself becomes a Malaysian-owned mapping asset, not a licensed foreign one.
The gateway contract · /exchange/v1
Three push messages in — pseudonymous speed samples, coarsened incident reports, one-tap verify verdicts — and one fused road state out. Versioned in the path, additive within v1. Any field that looks like a device id, phone, plate or trajectory is rejected at the schema layer, not by policy.
Fusion & trust engine
Speed-window fusion, reporter-trust decay, spam quarantine, corroboration folds — not speculative maths on a slide, but the exact engine already running in AnOmbak's production gateway. AnTIE adds a single new axis, member_id, threading ingest through trust to tiered pull.
The crowd-verify loop
Reports mature through verdicts. A fold needs distinct member × pseudonym pairs, so two different companies' drivers agreeing outweighs two users of one app — consensus cannot be farmed from inside a single crowd, and a lone tip becomes trusted faster.
Reciprocity metering
Pull quality is a deterministic function of contribution: contributors stream real-time; a member that stops pushing degrades live → delayed → coarsened, never a hard cliff. The tier is published on handshake, so it is auditable by every member rather than a black-box favour.
The member council
One member, one voice — regardless of size or contribution volume. The founding contributor holds no veto and no preferential data access. Spec changes, admissions and expulsions are Council decisions with reasons recorded, structured for Competition Act 2010 sign-off.
ITS-estate ingestion
Malaysia already pays for AI signal control, highway CCTV and operator control rooms. AnTIE asks for no new hardware — it exposes that paid estate as authoritative, machine-readable segment indications the crowd then verifies, turning fixed-sensor video into open road data.
Reference implementation
The spec and a deterministically reproducible reference implementation live in a neutral open-source home. Any member can run its own instance against the same input and diff the fused output — proof the operator is not silently privileged — and may fork at any time. Neutrality is testable, not promised.
The round trip: push, fuse, pull
The barter is deliberately cheap — a few REST endpoints in, an enriched fused state back. Your users, brand, routing engine and pricing stay entirely yours; the road state is the only thing shared.
Member apps
push pseudonymous samples
Exchange gateway
/exchange/v1 — one contract
Fusion & trust
production maths + member_id
Fused state, pulled
aggregate consensus only
Three families of truth, one posterior
Every published road colour is a reliability-weighted blend across thin crowds, authoritative agency indications, and the verdicts that turn a tip into consensus — and only the crowd's weight grows with use.
every member's pooled drives — the density that opens the gate
agency CCTV, signals & incidents — regionally gold, verified by the crowd
cross-app confirm / deny — a lone tip becomes consensus
The rule that lets competitors hand this their data without fear: a segment publishes only when it has k distinct contributors (k ≥ 3); below that it reads unknown — never a guess, never a per-member row. The hub stores no trajectories and cannot re-identify a driver even under order; pseudonyms are salted per member so no two companies' bucket spaces ever overlap.
The parts above are plumbing. The intelligence layered on top — and the three hard refusals that keep it trustworthy — live on the frontier page.
See the intelligence the pool enables→Ready to build something intelligent?
Let's engineer your next product — from idea to launch.