Sapiens: A Brief History of Humankind

CHAPTER 13

Read It

History's winners look inevitable only because we only see the one path that happened. Harari asks why global unification took the specific form it did—why this religion, this economic logic, these political borders—when so many alternatives were plausible at the time. His answer is uncomfortable: contingency, not superiority. The victors didn't win because they were better for humanity. They won because of accidents, feedback loops, and self-replicating patterns that don't care about human welfare. Christianity conquered Rome despite starting as an obscure sect. Capitalism spread not because it made people happier but because it replicated well. The deeper historians dig, the more alternate paths appear plausible, not fewer. The past isn't a chain of necessity. It's one branch among many that happened to survive. That realization doesn't give us a crystal ball. It gives us something sharper: the knowledge that today's arrangements are also contingent, also replaceable.

Sapiens: A Brief History of Humankind — The Secret of Success, an AI-assisted InkMap created by HutouchuiOpen full image
InkMap created by 虎头锤 (Hutouchui) with AI assistance · It may contain errors

Draw It

The causal chain here is subtle. It's not that history has no causes; it's that the causes we can name don't add up to necessity. I framed the visual around the gap between explanation and inevitability. A historian can describe how Christianity won, but can't show it had to win. The reason is a special kind of unpredictability: human systems react to predictions about themselves. A market forecast changes the market. A revolutionary theory changes the revolution. That reflexivity breaks the clockwork model of history. The visual foregrounds this loop—expectations altering outcomes—because it's the mechanism that makes certainty impossible. What's left isn't chaos. It's a system where the past is legible but the future is not.

Rethink It

The aftermath of a decision is where this bites. We write postmortems that explain why a product failed, why a feature succeeded, why a migration went smoothly. The explanations are often accurate. But they subtly imply the outcome was determined by the factors we list. In reality, another team with the same code and the same metrics might have ended up elsewhere. The reason is that our own accounts change what we do next, which changes the next outcome. It's not that analysis is worthless. It's that analysis happens inside the system it describes, and the system reacts.

Take It With You

History can tell us how we got here. It cannot tell us we had to get here. The present is one surviving path among many that were equally possible. That's not a reason to stop acting. It's a reason to stop pretending the winners were chosen by anything but a mix of accident and replication.