Language Through a Systems Architect's Eyes

I approach language 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.

Human language combines sound or gesture, syntax, semantics, pragmatics, memory, social inference and cultural learning. Meaning depends on shared contexts as well as formal structure.

Where does state live?

Human language combines sound or gesture, syntax, semantics, pragmatics, memory, social inference and cultural learning. Meaning depends on shared contexts as well as formal structure.

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?

Protocol thinking clarifies syntax, encoding, convention and error handling, and it shows why successful communication requires some shared structure.

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?

Network protocols try to minimize ambiguity. Human language routinely exploits ambiguity, metaphor, implication and incomplete information because speakers infer one another's intentions.

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

Evolutionary theory, linguistics and information theory each illuminated different aspects of language without reducing it to one mechanism.

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.

Language lets humans externalize models of absent worlds: memories, plans, laws, mathematics and imaginary universes.

Did language merely improve communication, or did it create a new kind of shared reality?

Reading trail

• Darwin Online — On the Origin of Species
• Aeon — Information theory and life's origins

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