<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>PairGeek Blog</title><description>PairGeek is an open protocol for expressing human compatibility and partnership intent as structured, machine-readable data. Founded on the principle that meaningful connection deserves better infrastructure.</description><link>https://pairgeek.org/</link><language>en</language><item><title>Introducing PairGeek Schema v1</title><link>https://pairgeek.org/blog/introducing-pairgeek-schema/</link><guid isPermaLink="true">https://pairgeek.org/blog/introducing-pairgeek-schema/</guid><description>Why we need a protocol layer for human compatibility data, and what PairGeek Schema v1 provides.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>From Date-Me Docs to a Proper Protocol</title><link>https://pairgeek.org/blog/date-me-docs-to-protocol/</link><guid isPermaLink="true">https://pairgeek.org/blog/date-me-docs-to-protocol/</guid><description>Date-me docs proved demand for structured self-presentation. PairGeek formalizes the format.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Why Structured Profiles Beat Unstructured Introductions</title><link>https://pairgeek.org/blog/structured-profiles-beat-unstructured/</link><guid isPermaLink="true">https://pairgeek.org/blog/structured-profiles-beat-unstructured/</guid><description>Free-form introductions are high-noise, low-signal. Structured profiles shift the burden of filtering from human attention to machine logic.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>The Costs of Information Asymmetry in Human Networks</title><link>https://pairgeek.org/blog/costs-of-information-asymmetry/</link><guid isPermaLink="true">https://pairgeek.org/blog/costs-of-information-asymmetry/</guid><description>When two people cannot efficiently assess their compatibility, both pay a cost. Most of that cost is invisible.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>From Business Cards to Structured Data: A Natural Evolution</title><link>https://pairgeek.org/blog/business-cards-to-structured-data/</link><guid isPermaLink="true">https://pairgeek.org/blog/business-cards-to-structured-data/</guid><description>The business card, the CV, the LinkedIn profile, the date-me doc: each iteration adds more structure. PairGeek is the next step.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Agent-Mediated Introduction: What It Looks Like in Practice</title><link>https://pairgeek.org/blog/agent-mediated-introduction/</link><guid isPermaLink="true">https://pairgeek.org/blog/agent-mediated-introduction/</guid><description>Before two people meet, their agents could already have exchanged compatibility scores, checked hard constraints, and issued a contact token. Here is what that looks like.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>The Handshake Problem: Pre-Screening as a First-Class Concern</title><link>https://pairgeek.org/blog/handshake-problem/</link><guid isPermaLink="true">https://pairgeek.org/blog/handshake-problem/</guid><description>Most compatibility failures are detectable before any human interaction occurs. Pre-screening is not unromantic — it is efficient.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>The Missing Link Between Personal Branding and Machine Readability</title><link>https://pairgeek.org/blog/personal-branding-machine-readability/</link><guid isPermaLink="true">https://pairgeek.org/blog/personal-branding-machine-readability/</guid><description>Personal branding is the human-readable layer. Machine readability is the missing layer underneath it. PairGeek connects the two.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Why pairgeek.txt Belongs Next to robots.txt</title><link>https://pairgeek.org/blog/pairgeek-txt-next-to-robots-txt/</link><guid isPermaLink="true">https://pairgeek.org/blog/pairgeek-txt-next-to-robots-txt/</guid><description>robots.txt tells crawlers what not to index. pairgeek.txt tells agents who you are and what you are looking for. The convention is the same.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Decentralized Discovery: How Crawlers Could Replace Matchmakers</title><link>https://pairgeek.org/blog/decentralized-discovery/</link><guid isPermaLink="true">https://pairgeek.org/blog/decentralized-discovery/</guid><description>A matchmaker is a centralized index of people. A crawler that understands PairGeek Schema can build the same index without any central authority.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Why Self-Sovereign Identity Matters for Human Pairing</title><link>https://pairgeek.org/blog/self-sovereign-identity-human-pairing/</link><guid isPermaLink="true">https://pairgeek.org/blog/self-sovereign-identity-human-pairing/</guid><description>Self-sovereign identity means your identity data lives on infrastructure you control. For human pairing, this changes who has leverage.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item></channel></rss>