Gene Regulation Through a Systems Architect's Eyes

I approach gene regulation 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.

Gene regulation controls when, where and how strongly genes are expressed. Transcription factors, DNA accessibility, chromatin state, RNA processing, signaling and cellular history all contribute to whether a sequence participates in current behavior.

Where does state live?

Gene regulation controls when, where and how strongly genes are expressed. Transcription factors, DNA accessibility, chromatin state, RNA processing, signaling and cellular history all contribute to whether a sequence participates in current behavior.

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?

Engineers know that code existing in a repository is different from code executing in production. Gene regulation offers a related distinction between capability, activation and context.

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?

Feature flags are intentionally designed and usually binary enough to audit. Biological regulation is evolved, overlapping, noisy, graded and deeply coupled to the physical state of the cell.

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

Work on gene regulation transformed the old one-way picture of genes issuing instructions into a layered view of conditional expression and feedback.

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.

Regulation weakens simplistic genetic determinism: possessing information is not equivalent to using it.

If many cell identities share almost the same genome, is identity stored in the library or in the pattern of access?

Reading trail

• NHGRI — Gene Regulation
• Quanta — The Math That Tells Cells What They Are
• Aeon — We are not machines

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