The Substitution Escrow Threshold: When "Compatible With" Becomes Safe Enough to Buy
arXiv:2608.21221
Abstract
Enterprise infrastructure buyers routinely evaluate compatibility claims--"S3-compatible," "PostgreSQL-compatible," "OpenAI compatible"--as proxies for future substitution options. Yet most compatibility claims do not escrow the substitution path they imply. This paper introduces the Substitution Escrow Threshold, a five-condition framework that determines when a compatibility claim genuinely reduces institutional risk versus merely reducing first-integration cost. The five conditions--boundary closure, executable conformance, custody independence, state and operations reversibility, and extension quarantine--are applied to five infrastructure cases (OCI, Kubernetes, OpenTelemetry, S3, PostgreSQL) that populate five distinct outcome cells. The framework produces actionable diagnostics for enterprise architects, platform engineers, procurement teams, and investors evaluating compatibility-dependent infrastructure decisions, and identifies AI infrastructure as the framework's most urgent next application.
21 pages, 5 tables. Framework paper with worked public-record assessment; validation study is separate future work