Civilization Through a Systems Architect's Eyes

I approach civilization with an occupational habit: I want to draw boxes and arrows. That habit is useful because architecture forces questions about state, boundaries, interfaces, resources and failure. It is dangerous because natural systems were not designed to respect our diagrams.

Civilization depends on layered systems of food, energy, communication, law, infrastructure, trade, knowledge, trust and institutions. No single participant understands or controls the whole.

Where does state live?

Civilization depends on layered systems of food, energy, communication, law, infrastructure, trade, knowledge, trust and institutions. No single participant understands or controls the whole.

Software gives us the expectation that important state should have an owner. Natural systems often distribute state across structure, concentrations, relationships and history. A snapshot can therefore tell us less than the process that produced it.

Where are the interfaces?

Distributed-platform language is useful because societies genuinely rely on standards, shared state, redundancy and coordination among partially independent actors.

Engineered interfaces are declarations. Natural boundaries are often material: membranes, tissues, ecological borders, channels, gradients or social conventions. They can leak, adapt and participate in the behavior they constrain.

What is the failure model?

People are not passive services. They have beliefs, incentives, power and the ability to reinterpret or change rules, so efficiency alone cannot describe a human system.

Failure analysis is useful because normal operation hides assumptions. A healthy component can coexist with an unhealthy whole. A local optimization can damage the larger system. Robustness at one level can create fragility at another.

History is part of the architecture

Large societies repeatedly expanded coordination through writing, accounting, roads, money, bureaucracy, printing, telecommunications and digital networks.

In a designed system, legacy structure may be accidental baggage. In an evolved or historically accumulated system, legacy structure can be the reason the current architecture exists at all. The path is not documentation around the system; sometimes it is part of the system.

The zoom test

A good architectural description should survive zooming. Going down a level should reveal mechanisms capable of implementing the higher-level pattern. Going up should reveal regularities that justify discussing the larger entity in its own vocabulary.

Civilization is a human artifact that no individual designed. We inherit it, alter it and depend on systems whose complexity exceeds any one mind.

Who is responsible for a system that everybody influences but nobody fully controls?

Reading trail

• The Carl Sagan Portal
• Aeon — Life as a restless manner of being

These links are starting points for the scientific and historical ideas. The systems interpretation, analogies and conclusions here are my own.