Book

Coupling

Cohesion, Consequence, and the Architecture of Responsibility

A practical framework for seeing where systems are tightly joined, where they drift apart, and how those coupling choices shape accountability over time.

Focus in observatory Download EPUB Download Word (DOCX)Download PDF

Major concepts

Concept

Abstraction

Abstraction is mediation away from direct encounter: compression of complexity as systems scale, valued when it preserves accountability signal at the boundaries where behavior can still be redesigned—and costly when it hides consequence until feedback arrives too late.

Concept

Accountability

Accountability is exposure to consequence: who can see effects, who can be challenged or redirected, and whether authority stays close enough to lived outcomes for correction to remain plausible.

Concept

Agency

Agency is the practical capacity to initiate action that can affect outcomes. Formal role without real leverage is low agency, even when nominal responsibility remains.

Concept

Agile

Agile is used in a software engineering sense. Agile refers to iterative development approaches that shorten feedback cycles, emphasize incremental delivery, and increase team-level ownership of ongoing change.

Concept

Authority

Authority is operational coordination power—the recognized right to steer, allocate, or constrain action—always in tension with legitimacy and with whether consequence stays visible enough under scale for coordination to remain contestable rather than brittle.

Concept

Circulation

Circulation is transmission and reproduction through systems: how norms, habits, and design choices move, repeat, and amplify—what spreads without being re-owned locally, and what keeps learning alive as coordination widens.

Concept

Cohesion

The degree to which responsibility is clearly held within a boundary (team, role, function, or institution). High cohesion means ownership is legible and decisions are not diffusely assigned.

Concept

Constraints

Constraints are the limits and boundary conditions that shape what actions are possible in a system. They include technical limits, legal rules, time pressure, budget limits, and institutional procedures. Good constraints channel behavior toward learning and accountability; poor constraints hide tradeoffs or displace consequence.

Concept

Contract

Contract is used in a software engineering sense. A contract is the explicit behavioral agreement attached to an interface: what inputs are valid, what outputs are expected, what errors can occur, and what invariants are guaranteed. Strong contracts reduce ambiguity between components and make failures easier to diagnose.

Concept

Correction

Correction is reality-contact and revisability: the lived work of noticing mismatch, updating beliefs or behavior, and narrowing the gap between what was assumed and what is actually happening before drift hardens into normal.

Concept

Coupling

Coupling is attachment between action and consequence—how tightly decisions remain traceable to effects, how feedback travels, and whether redesign authority can still bite when scale and abstraction lengthen the chain.

Concept

DevOps

DevOps is used in a software engineering sense. DevOps refers to practices and operating norms that reduce the distance between software implementation and operations so that delivery, reliability, and learning stay structurally connected.

Concept

DORA

DORA is used in a software engineering sense. DORA refers to research-backed software delivery metrics and practices (for example, lead time for changes and change failure rate) used to evaluate learning-loop quality between development and operations.

Concept

Feedback

The path by which outcomes return as signal and influence future decisions. Weak or delayed feedback reduces learning quality.

Concept

Governance Coupling

The degree to which formal oversight structures preserve real consequence return to decision-capable authority. Governance coupling weakens when signal is filtered, delayed, or politically insulated, even if nominal accountability mechanisms still exist.

Concept

Hexagonal Architecture

Hexagonal architecture is used in a software engineering sense. Hexagonal architecture (also called ports and adapters) is a boundary pattern that keeps domain logic insulated from external technologies by routing integration concerns through explicit interface ports and adapter implementations.

Concept

Incentives

Incentives are the reward and penalty patterns that influence behavior over time. Incentives include formal metrics, promotion logic, political pressures, funding structures, and social recognition patterns. Incentives do not determine behavior by themselves, but they strongly bias what actors optimize for.

Concept

Interface

Interface is used in a software engineering sense. An interface is the defined boundary through which one component interacts with another (for example, function signatures, API endpoints, message schemas, or protocol expectations). A good interface makes dependencies explicit while minimizing exposure to internal implementation details.

Concept

Invariant

A condition that should remain stable across contexts and scale if a system is to stay healthy. The invariant is that responsibility should remain cohesive and consequence should remain intentionally coupled.

Concept

Judgment

Judgment is deliberate evaluation under uncertainty: slowing automatic escalation long enough to weigh tradeoffs honestly, keep coordination aligned with consequence rather than with speed alone, and preserve room for contestability.

Concept

Legitimacy

Legitimacy is justified recognition of authority—whether power reads as earned and contestable enough that coordination holds under stress instead of collapsing into cynicism, performative compliance, or hidden veto by drift.

Concept

Operational Coupling

The degree to which the people who design or decide also remain close to execution and runtime consequence. Operational coupling is stronger when builders, operators, and reviewers share consequence exposure. It is weaker when handoffs separate decision authority from incident impact.

Concept

Renewal

Renewal is restoration of legitimacy and correction: deliberate moves that reopen feedback, shorten consequence distance, and pull a stretched system back toward workable exposure to reality before erosion becomes the new baseline.

Concept

Responsibility

Responsibility is the durable relation between action and answerability. It includes not only causal involvement but also the obligation to account for consequences and respond to what is revealed by them.

Concept

Scale

Scale is coordination beyond direct relational encounter—growth in size, complexity, or abstraction layers that increases distance between decisions and consequences and therefore changes how cohesion, coupling, and feedback must be engineered to stay learnable.

Concept

Shift Left

Shift left is used in a software engineering sense. Shift left means moving quality, security, and risk checks earlier in the development lifecycle rather than concentrating detection late in integration or release.

Concept

System

A system is an organized set of people, processes, rules, and structures that produces repeatable outcomes over time. The term applies across domains: software architectures, teams, firms, agencies, governance structures, and media institutions. The shared criterion is not technology; it is patterned behavior under constraints, incentives, and feedback.

Concept

Temporal Coupling

The degree to which consequences return quickly enough to shape near-term decisions. Strong temporal coupling shortens the time between action and correction. Weak temporal coupling introduces lag, memory loss, and interpretive noise that can protect failing designs from timely revision.

Concept

Waterfall

Waterfall is used in a software engineering sense. Waterfall refers to a phase-sequenced development model where requirements, design, implementation, testing, and release are treated as largely distinct stages with formal handoffs and review gates.

Major patterns

Pattern

Dissent is Welcomed

Problems, risks, or failures show up inside a group or setting. Timely correction depends on whether bad news can reach those who decide. - Speaking up can cost people socially or at work - Reporting lines filter or delay information - Good news travels easier than bad news - People learn what is safe to say Problems show up early. Reality reaches those who decide in time. If you see a problem, say it now. Dissent is welcomed here—we can't fix what we don't raise while it's still small.

Pattern

Examples Accumulate

A leader reacts to a mistake, competing pressures, or unclear ground in a shared setting. People need to know what counts as OK. Clear rules are missing or thin. - People watch others when things are unclear - What people see moves faster than written rules - Early reactions set what feels allowed - Silence and emphasis both send a signal What the leader does—especially under pressure—quickly sets what others treat as acceptable. Careful what we model in the room; examples accumulate faster than anything we post on the wiki.

Pattern

Exceptions are Forever

A group adopts emergency measures or exceptions during a crisis or rush. Moves made for speed or survival do not always roll back when things calm down. - Urgency justifies skipping normal limits - Short-term wins reinforce the exception - Rolling back takes effort and coordination - New ways of working turn into habit fast Workarounds and shortcuts turn into how the group works day to day. Let's be careful carving out another exception—exceptions are forever, and this one will outlive the emergency we made it for.

Pattern

Feedback Drives Change

New facts, visible risk, or bad assumptions show up after direction is set. The group must choose: change course or protect the public story and what people already signed up for. - Going public makes reversal costly - Momentum favors staying the course - Saying we were wrong can threaten legitimacy - Small fixes are easier than full reversals The group shifts direction based on new facts or new risk. We're not wed to yesterday's plan—feedback drives change, and what we learned this morning changes what we ship.

Pattern

Learning Collapses

Those who decide sit far from where effects show up. News from the ground does not reliably reach them in time. - Size adds distance from impact - Formal reporting filters or delays signals - Bad news is costly to raise - Good news travels easier than bad news They do not get a clear read in time on what their choices are doing. We're steering off summaries again. Learning collapses when the ground story never reaches this room.

Pattern

Meaning Gets Distorted

A provisional interpretation is repeated without re-exposure to source context. Coherence is preserved at the expense of accuracy. - Confirmation bias filters incoming data - Social reinforcement rewards consistency - Identity defense resists revision Interpretation can harden in ways that no longer track reality. Meaning gets distorted when certainty outlives contact with what was actually said.