01 Get involved
Community
GID is meant to be shaped in the open, with explicit provenance. The standard is better the more it is argued with - so the channels below are the standard, not a marketing afterthought.
GitHub
The specification, the reference implementation, and every design decision in the open. Issues and discussions are where proposals are argued.
Open → Real-timeDiscord
Day-to-day conversation with the people building GID and the first devices. Bring questions, hardware, and disagreement.
Open → ReferenceSpecification
The normative standard and developer documentation, rendered at gid.pekelabs.com as it stabilizes.
Open → DirectContact
Reach PeKe Labs directly for partnership, hardware, or press.
Open →02 How to help
Where contributions matter most
- Pressure-test the thesis. If HID already solves addressing somewhere, we want to know before we build on the assumption that it does not.
- Bring platform reality. Concrete behavior of iOS, Android, macOS, and Windows over BLE - background execution, locked-device limits, MTU - shapes what GID can require.
- Argue the foundations. The envelope, how GID versions and extends, and the addressing model are where review is worth the most.
- Build a device. The fastest way to find a flaw in a standard is to implement it against real hardware.
03 Provenance
Who stewards GID
GID is stewarded by PeKe Labs and intended as an open, community-shaped standard. Governance - licensing, how decisions are ratified, and who owns the extension registry - is itself an open question being worked through in public. As that settles, the contributor and governance documents will live alongside the specification.
Introduced at AWE XR 2026.