Field Geometry in Practice Two Protocols for the Coordination Economy

Abstract

The first two papers of this series established, respectively, an empirical diagnosis of extractive economic structure and a formal theory of why such structures transition and what a coordination-respecting successor must be built of. This paper supplies the missing third element: concrete protocol specifications audited against the theory's own design criteria. Two cases are examined. The first is a credentialing crisis in elite corporate recruitment: the university degree, this paper argues, was never primarily a certificate of skill but a costly, compliance-based proxy for coordination capacity (Spence, 1973), adopted because coordination is expensive to verify directly and because executive review time — the scarce resource the credential filter economizes — is itself a coordination-bandwidth constraint, finite and unforceable in exactly the sense the second paper formalized. The paper's central technical contribution is the Adversarial Anti-Derivative Filter, an algorithm that restores direct, low-latency evaluation of coordination capacity at scale by generating a model's own baseline solution distribution and filtering submissions by their semantic distance from it — a computable test for the compliance/coordination distinction, situated against the AI-generatedtext detection literature and its documented arms-race limitations. The second case is shippingrouter, a local-first, open-source logistics telemetry protocol, audited section by section against the second paper's design triad: an open sink (value dissipates as demurrage avoided and labor saved, never re-accumulating as a token or reservoir), the absence of stock-accumulable gains, and universal forkability, with one terminological correction — the protocol's “zero-knowledge telemetry” is precise anonymized aggregation, not zero-knowledge proof, and the paper restates the mechanism accordingly. A supply-chain case study unifies both protocols under the second paper's stock/flow distinction: legacy enterprise software records participation after the fact, while a semantic telemetry layer detects coordination failure — the ripple not yet connected — before the flow-based checkpoint trips. The paper closes with a generalized protocol grammar, a checklist against which future builders can audit new architectures, and a set of counterarguments including the filter's own adversarial ceiling and Goodhart's law.