Coherence as Infrastructure

Beneath every economy lies a culture. Beneath every culture lies a set of relationships. Beneath every relationship lies a nervous system. And beneath every enduring civilization lies a capacity for coherence.

— The Coherence Thesis, Vol. I

Every enduring civilization eventually discovers the same truth: survival depends less on the accumulation of power than on the quality of relationship governing how power moves through the system.

History demonstrates this repeatedly. Civilizations rarely collapse because they become incapable of generating intelligence, wealth, or technological sophistication. Many collapse while possessing extraordinary technical power. Rome mastered engineering while political legitimacy deteriorated beneath it. Industrial civilization generated immense productive capacity while destabilizing the ecological systems sustaining it. Digital civilization connected billions of people while progressively fragmenting the relational and attentional conditions required for coherent coordination. Again and again, societies become more powerful while simultaneously becoming less trustworthy with power.

Part I described this condition from the inside out: nervous systems overwhelmed by environments they cannot metabolize, relationships degraded by communication systems that strip away regulatory feedback, institutions optimizing extraction while remaining structurally blind to the substrates sustaining them. The diagnosis was necessary because civilization cannot become coherent through inaccurate descriptions of itself. But diagnosis alone is insufficient. A civilization cannot survive indefinitely by becoming more articulate about its collapse.

At some point the question must shift from what is breaking down? to what would have to be built?

This chapter begins that work, and it does so by naming a project rather than gesturing toward one. The remainder of this book is partly the founding document of an attempt at that work—a coordination infrastructure called Providence, currently in early design, with an MVP built but no public version operating.

The chapters that follow describe what Providence is, what it intends to become, where the architecture remains unresolved, and why this kind of infrastructure has become necessary. Part of the book’s purpose is to invite the people who could build it—software engineers, coders, designers, governance practitioners, contemplatives, ecologists—into the work of building it. Providence is offered less as a finished proposal than as a structure worth building, an idea concrete enough to be developed and serious enough to be worth developing well.