Mathematics Through a Systems Architect's Eyes

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

Mathematics constructs formal structures from definitions, relations and inference. In science its power comes from mapping aspects of physical systems onto structures from which consequences can be derived.

Where does state live?

Mathematics constructs formal structures from definitions, relations and inference. In science its power comes from mapping aspects of physical systems onto structures from which consequences can be derived.

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?

Software architecture also lives by abstraction: a good model compresses many cases while preserving the invariants that matter.

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?

A mathematically correct model can still encode the wrong physical assumptions. Certainty inside a formal system is not the same as empirical certainty about the world.

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

Greek mathematical traditions tied proof, ratio and geometry to philosophical questions; the historical Pythagoras is particularly hard to reconstruct because no securely attested writings survive.

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.

Mathematics is where symbolic reasoning most dramatically escapes immediate experience and then returns with predictions about reality.

Do mathematical structures describe reality because we selected useful structures, because reality is mathematical, or because the distinction is incomplete?

Reading trail

• Stanford Encyclopedia of Philosophy — Pythagoras
• Stanford Encyclopedia of Philosophy — Pythagoreanism

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