UODI encodes transport demand — road, air, maritime, rail, subterranean, orbital — into a fixed 15-block machine-readable string. No schema agreement. No middleware. Any parser reads any conforming string.
When you submit a transport request, your data belongs to the platform you used. Want to switch providers? Start from scratch. Want to connect your ERP to a carrier's system? Pay months of integration work. If the message is modified in transit, there's no way to detect it at the encoding layer.
There is no common language between systems. Every platform speaks its own dialect. The request is not yours — it belongs to them.
UODI solves all three: an open standard any system reads without prior integration, built-in progressive geospatial privacy, and intention integrity in every string.
As a side effect: 50–70% less data per message means measurable bandwidth and energy savings on satellite and IoT links — where every byte has a cost.
POST /api/v2/quote HTTP/1.1
Host: carrier-platform.com
Authorization: Bearer eyJhbGci...
{
"origin": { "lat": 40.7128, "lon": -74.0060,
"address": "123 Wall St, NY" },
"destination": { "lat": 51.5074, "lon": -0.1278,
"address": "10 Downing St, London" },
"cargo": { "weight_kg": 500, "type": "valuables",
"owner": "ACME Corp", "insured": true },
"requester_id": "usr_8f3kd92",
"timestamp": "2026-03-07T14:32:00Z"
}
→ Full address exposed before any agreement.
→ Locked to this platform's schema.
→ No integrity guarantee on the payload.
P120-VALO-ROAD-ARMD-CRIT-URGE-HUMA-****-XOM6LP4Z-K0500-DR5RS0__________-????????????????-070326-M030-CD47
→ Destination is a placeholder until confirmed.
→ Any system reads this. No prior agreement needed.
→ CHK4 anchors the original intent. Tamper-evident.
Fixed-width positional parsing. Point to a memory offset and you have the field. Works on any platform, any language.
# Any UODI v1.2 string wire = "P120-VALO-ROAD-ARMD-CRIT-URGE-HUMA-****-XOM6LP4Z-K0500-DR5RS0__________-????????????????-070326-M030-CD47" blocks = wire.split("::")[0].split("-") fields = { "version": blocks[0], # P120 "mode": blocks[1], # VALO "type": blocks[2], # ROAD "prop": blocks[3], # ARMD "quantity": blocks[9], # K0500 "origin": blocks[10], # zone only "dest": blocks[11], # locked: ???????????????? "chk4": blocks[14], # CD47 } dest_locked = fields["dest"] == "????????????????" # True — destination sealed until revealed
// Any UODI v1.2 string const wire = "P120-VALO-ROAD-ARMD-CRIT-URGE-HUMA-****-XOM6LP4Z-K0500-DR5RS0__________-????????????????-070326-M030-CD47"; const blocks = wire.split("::")[0].split("-"); const fields = { version: blocks[0], // P120 mode: blocks[1], // VALO type: blocks[2], // ROAD prop: blocks[3], // ARMD quantity: blocks[9], // K0500 origin: blocks[10], // zone only dest: blocks[11], // locked: ???????????????? chk4: blocks[14], // CD47 }; const destLocked = fields.dest === "????????????????"; // true — destination sealed until revealed
Like telling a taxi "I'm somewhere in the north of the city." Every carrier can evaluate whether they cover that zone. Only the one you choose gets the exact address. The others never know where you were — or where you were going.
ORIG and DEST encode 3D geospatial coordinates in exactly 16 characters using the format [GEOHASH_12][SIGN][ZZZ].
The geohash is right-padded with underscores to 12 characters. Fewer characters = less precision = more privacy. The padding character is unambiguous: underscore is not in the geohash alphabet.
The Z-axis encodes altitude above ground (+), depth below surface (−), or ground level (0) in metres. The same format covers drone delivery pads at +120m, tunnel logistics at −15m, and orbital demand via the ::TRAJ extension.
In Phase 1, DEST is set to ???????????????? — fully incognito. After bilateral handshake, the exact 3D coordinate is disclosed and verified against the CHK4 commitment.
| Mode | Example | Precision | Use Case |
|---|---|---|---|
| Exact | AR69Y7PGXQWT+120 | ~3.7 cm | Drone pad · robotic docking |
| Reduced | AR69Y7PG____0000 | ~610 m | City block |
| Vague | AR69Y7______0000 | ~±20 km | Region · pre-handshake |
| Incognito | ???????????????? | None | Locked until handshake |
An international logistics operator must deliver sensitive cargo to a corporate campus or military installation. The recipient does not want carriers to know the exact location before the service is confirmed. The facility does not admit vehicles without a validated mission.
The emitted UODI publicly declares: zone, cargo type, handling conditions. The exact destination is a placeholder — there is no data to intercept because the exact data was never emitted. When the carrier confirms the service, the emitter reveals the real coordinates. The receiving system recalculates the CHK4: if it matches the originally emitted value, the data is authentic and unaltered. The facility scans the code at the access point and verifies the mission on the spot.
Comparative analysis against the most widely deployed logistics data formats. Scenario: 1 million messages per day on a standard cloud vCPU.
| Capability | UODI | JSON / REST | XML / EDI | Freight Platform | IoT Framework |
|---|---|---|---|---|---|
| Pre-contract demand broadcast | ✓ Native | ✗ | ✗ | ⊘ Closed | ✗ |
| No prior API agreement needed | ✓ | ✗ | ✗ | ✗ | ⊘ Complex |
| Progressive location privacy | ✓ Structural | ✗ | ✗ | ✗ | ✗ |
| Native 3D location (Z-axis) | ✓ | ⊘ Manual | ⊘ Manual | ✗ | ⊘ Manual |
| O(1) positional parsing | ✓ | ✗ Tree | ✗ Tree | ✗ | ✗ |
| Transport-layer independent | ✓ UDP/MQTT/SAT | ✗ HTTP | ✗ HTTP/AS2 | ✗ | ⊘ Varies |
| Embedded / IoT ready (<300 lines) | ✓ | ✗ | ✗ | ✗ | ⊘ Heavy |
| Tamper-evident integrity (CHK4) | ✓ CRC-16 | ✗ | ⊘ Envelope | ✗ | ⊘ Optional |
| Vendor-neutral, open standard | ✓ | ⊘ Schema varies | ⊘ Mapping needed | ✗ Proprietary | ⊘ Varies |
Benchmark figures derived from comparative analysis of 1M message workloads. CPU times reflect standard cloud vCPU positional vs tree-parse implementations. Data volumes based on median payload sizes per format.
UODI v1.2 is fully specified and production-ready. The reference validator, canonical examples, and complete specification are available on GitHub. Patent licensing, commercial certification, and implementation partnerships available through the author.