Skip to content
AFTER CERTAINTY
Skip to chapter text

CouplingPart I - The Structural Grammar

Bridge - Into Part I

BridgeAbout 2 mins

The prologue introduced a recurring pattern: responsibility drifts away from consequence, authority drifts away from cost, and systems continue functioning while becoming harder to correct. The examples differed—software incidents, institutional failures, public accountability, organizational drift—but the structure underneath them was surprisingly similar.

Part I slows down before moving into larger case studies and asks a more basic question: what has to happen inside a system before that kind of drift becomes possible?

The Grammar Beneath the Pattern

The first chapters introduce two ideas that will appear throughout the rest of the book: cohesion and coupling. These terms come from software design, but the book uses them more broadly. Cohesion describes whether responsibility remains clear enough that someone can still answer for outcomes and redesign the system when necessary. Coupling describes whether consequences can still return clearly enough for learning to happen before explanation replaces correction.

These ideas matter because systems often fail gradually. Ownership becomes less clear, feedback arrives later, coordination overhead increases, and reports improve while operational reality drifts. The system remains active, but learning weakens.

Why Scale Changes Everything

Part I also introduces the pressure that makes these problems harder over time: scale. As systems grow, more boundaries appear, more abstraction becomes necessary, and more coordination is required simply to maintain shared understanding. Those pressures do not automatically destroy accountability, but they make accountability increasingly difficult to preserve structurally.

Healthy systems therefore require more than good intentions. They require boundaries clear enough for responsibility, coupling strong enough for learning, and feedback paths short enough that consequence can still change behavior before drift hardens into routine.

The rest of the book builds from this grammar outward: first through software, then through institutions, and finally through the limits large systems can never fully escape.