The technical foundation, in 23 pages.
An air traffic protocol for the low-altitude century — altitude-direction encoding, hexagonal cells, 4D reservations, and an AI communication layer with mandatory deterministic fallback.
versky-whitepaper-v1.0.pdf
Citation-ready, email-attachable, plain-PDF — no DRM, no watermark, no tracking.
What the whitepaper proposes.
The next decade will place between ten million and one hundred million autonomous and semi-autonomous aerial vehicles into the airspace below five hundred metres. Existing air traffic management infrastructure was not designed for this regime, cannot be cost-effectively retrofitted, and will not scale.
VerSky™ proposes a new protocol layer for that airspace, resting on three load-bearing ideas: altitude that carries direction of travel, hexagonal cells that map one-to-one onto a six-direction movement alphabet, and a four-dimensional reservation primitive whose coordination cost is constant per request. An AI communication layer — AACP — negotiates routing creatively between vehicles, while the safety of the airspace itself rests on a deterministic fallback that runs identically on every vehicle when negotiation fails.
The protocol is the subject of two non-provisional US patent applications filed February 27, 2026 (Application Nos. 19/551,620 and 19/551,624). The reference implementation will be released under an open-source licence (terms TBD) in a future phase.
Seven principles, each load-bearing.
The protocol's design is governed by seven principles. Each is intended to be removable only at the cost of a material property. Chapter 3 of the whitepaper elaborates.
Altitude Encodes Direction.
4D Space-Time Reservation.
Hex-Cell Capacity.
Speed Scales with Height.
Priority by Purpose.
Fail-Safe = Descend.
Digital-Only Infrastructure.
Nine chapters and two appendices.
The structure is linear by design — chapters 1–3 establish motivation, 4–6 describe the three technical layers, 7 situates against existing systems, and 8–9 cover adoption and patent status.
How to cite this document.
For academic correspondence or to request a citable archival mirror, write to hello@versky.org.