PairGeek Schema Specification
The formal specification for PairGeek Schema v1 — a machine-readable vocabulary for expressing human compatibility and partnership intent.
Abstract
PairGeek Schema defines a machine-readable vocabulary for expressing human compatibility and partnership intent. It extends schema.org/Person with six namespaced property groups: identity, compatibility, lifecycle, interaction, signal, and agent.
Layer 0 — Namespace & Versioning
The PairGeek namespace is rooted at https://pairgeek.org/schema/v1. Semantic versioning is embedded in the URL path. Minor versions (v1.1, v1.2) add properties only; structural changes require a major version bump (v2).
{
"@context": [
"https://schema.org",
"https://pairgeek.org/schema/v1",
{ "pg": "https://pairgeek.org/schema/v1#" }
]
}Layer 1 — Discovery Protocol
Per RFC 8615, the primary machine-readable manifest is served at /.well-known/pairgeek. A human-readable pairgeek.txt at the domain root follows robots.txt convention.
// /.well-known/pairgeek
{
"schema_version": "1.0",
"status": "open",
"seeking": ["lifelong", "intellectual-collaborator"],
"schema": "https://yourdomain.com/pairgeek.json",
"contact_gate": "https://yourdomain.com/contact",
"last_updated": "2026-04-07T00:00:00Z",
"ttl": 86400
}Layer 2 — Core Schema
Six property namespaces extend schema.org/Person: pg:identity (cognitive profile, expertise, language), pg:compatibility (hard constraints, soft preferences, dealbreakers), pg:lifecycle (location, time allocation, financial model), pg:interaction (communication mode, conflict style, attachment), pg:signal (verifiable credentials, DID, ZK proofs), pg:agent (access policy, auto-reject rules, negotiation protocol).
Layer 3 — Variants System
Variants are expressed as RFC 6902 JSON Patch documents applied to a base schema. This allows contextual forks (lifelong partner, intellectual collaborator, project co-founder) without maintaining separate full documents.
{
"base": "https://yourdomain.com/pairgeek.json",
"variants": {
"lifelong": { "patch": [], "visibility": "public" },
"collaborator": {
"patch": [
{ "op": "add", "path": "/pg:compatibility/project_scope", "value": "research|venture" }
],
"visibility": "on-request"
}
}
}Layer 4 — Agentic Documentation
Markdown documents embed pg: YAML front-matter so the same file serves both human readers and RAG-based agents. Each section carries pg_salience (0–1) and pg_chunk_type for semantic search metadata.
Layer 5 — Trust & Verification
W3C Verifiable Credentials and DID-based identity allow claims to be cryptographically attested without centralized issuers. ZK Range Proofs enable disclosure of ranges (e.g., age 25–30) without revealing exact values.
Layer 6 — Agent Negotiation Handshake
Before any human contact, agents exchange PAIRGEEK_HELLO and PAIRGEEK_SCORE messages to complete compatibility scoring and hard-constraint checks. A contact_gate token is issued only on pass.