Introducing PairGeek Schema v1
Why we need a protocol layer for human compatibility data, and what PairGeek Schema v1 provides.
The dating app paradigm is broken by design. Swipe interfaces optimize for engagement metrics, not compatibility. Profile formats are proprietary, non-portable, and opaque to any analysis beyond the platform's own recommendation algorithm.
PairGeek Schema takes a different approach: treat compatibility data as a first-class protocol, not a platform feature. Define a vocabulary. Publish it as JSON-LD. Let anyone implement it on their own domain.
The result is a profile that any agent can read, any human can inspect, and any crawler can index — without requiring a centralized platform to exist.
Schema v1 defines six property namespaces: identity, compatibility, lifecycle, interaction, signal, and agent. Each namespace is independently extensible. The whole document is hosted at a URI you own and control.
We are publishing the spec today. Implementations, SDKs, and agent reference code will follow.