Application No.
19/551,620
Conf. #6812
Altitude-Direction Encoding Protocol for Air Traffic Management with Hexagonal Grid and Intersection Separation
- Filed
- Feb 27, 2026
- Claims
- 20
- Status
- Pending USPTO examination
Trust · License · Legal
The legal stack, plainly.
Patent status, licensing terms, privacy practices, and legal disclaimers — written to be read, not skimmed past.
§1 · Patent Status
Two non-provisional applications, filed Pro Se.
Both applications were filed with the United States Patent and Trademark Office on February 27, 2026 under Micro Entity status.
Application No.
19/551,624
Conf. #4598
AI Aerial Communication Protocol with Peer-to-Peer Negotiation and Deterministic Fallback Resolution
- Filed
- Feb 27, 2026
- Claims
- 20
- Status
- Pending USPTO examination
§2 · License
License terms — to be determined.
Final licensing terms for the forthcoming reference implementation are under consideration. They will be announced on this page ahead of the implementation's public release.
Commercial use
A licence is expected to be required for commercial implementations of the patented protocol — terms TBD.
Patent integrity
Every public statement on this site is reconciled against the filed patent specifications. The two non-provisional applications (Nos. 19/551,620 and 19/551,624) are the authoritative description of the protocol — public materials describe, but do not redefine, what is filed.
Research and non-commercial use
Independent research, academic citation, simulation reproduction, and non-commercial experimentation are intended uses of the protocol description. Final licence terms for the reference implementation will preserve these uses by design.
Implementation pre-release
A Python reference implementation exists in pre-release form and is available to qualified teams on request via the /implement page. Public distribution is gated on the licence decision.
Open governance plan
The intent is to engage standards bodies (ASTM F38, ICAO RPAS Panel) once the reference implementation matures. Governance terms — contributor agreements, reference-implementation maintainership, conformance testing — will be published alongside the licence.
Trademark
VerSky™ is a trademark of Jittapol Prukpatarakul. Use of the name in a manner that suggests endorsement requires permission.
§3 · Privacy
What this site collects.
What we collect: only email addresses you submit through the newsletter signup or contact form, plus the message you write. Newsletter delivery uses Resend. Inbox is hosted by Zoho Mail.
What we don't collect: no third-party tracking cookies, no advertising pixels, no cross-site behavioural profiling. No personal data is sold or shared. We may add privacy-preserving analytics (Plausible or Cloudflare Web Analytics) later — never trackers.
Newsletter: opt-in only. One-click unsubscribe in every email. We delete addresses on request — write to hello@versky.org.
VerSky Cloud (later phase): protocol telemetry retention policies, audit log access controls, and GDPR-compliant data subject rights will be documented before any production deployment.
§4 · Legal Disclaimer
What this site is not.
The information presented on this site is provided for educational and informational purposes only. It does not constitute legal, regulatory, or engineering advice. Specifications described herein may change before the VerSky™ protocol reaches v1.0.
Patent claims described or summarised on this site are not the official patent claims of record. The official claims are those filed with the United States Patent and Trademark Office and accessible via USPTO Patent Center.
The phrase “patent pending” refers to the filed but not yet examined applications listed in §1 above. No representation is made that any patent will issue or that any specific claim will be allowed.
The VerSky™ trademark is asserted as an unregistered common-law trademark. No registration with the USPTO has been completed at the time of writing. Use of ™ symbol is intended to provide notice of trademark claim.
Use of the protocol in any safety-critical system requires independent verification, certification, and regulatory approval. The author makes no warranties as to fitness for any particular purpose.
§5 · Contact
Standards bodies, regulators, researchers — get in touch.
Pick the inquiry type that fits, or email hello@versky.org directly. We typically respond within a few business days.