Functional Anatomy of Systems

The Question Under The Question

At the surface, the question sounds like organization design:

Why do companies have finance, infra, marketing, security, operations, HR, and so on?

But the deeper question is more interesting:

Why does every serious body, at every scale, seem to divide reality into offices of responsibility?

A family may not call it “operations,” but someone handles food, bills, repairs, care, memory, conflict, and planning. A school may not call it “risk,” but it has discipline, safeguarding, attendance, health, exams, and records. A government has ministries and local offices. A cell has organelles. A person has attention, memory, appetite, planning, emotion, immune response, and habits.

The names differ because the materials differ. The pattern remains because the pressure is the same:

1. too much reality
2. too many disturbances
3. too much memory required
4. too many conflicts
5. too many tasks
6. too many time horizons

Organization is one of humanity’s oldest technologies for turning that pressure into named responsibility.

The First Pressure: One Center Cannot Hold All Variety

Cybernetics gives the cleanest entry point. W. Ross Ashby’s law of requisite variety says that regulation requires enough variety to meet the variety of the thing being regulated. Put plainly: a controller that can only respond in three ways cannot govern a world that throws thirty different kinds of disturbance at it.Ashby’s own statement is about outcomes: “only variety in R can force down the variety due to D; variety can destroy variety.” The law sets a floor. With three responses to thirty kinds of disturbance, at least ten different outcomes get through, whatever the controller does (An Introduction to Cybernetics, 1956).

That insight is why centralization alone is not enough. A single center can set identity, priority, policy, and escalation paths. It cannot personally process every local detail without becoming blind, slow, or tyrannical.

This is where delegation becomes more than convenience. Delegation is not merely “I am busy, you do it.” It is the structural answer to excess variety.

Herbert Simon sharpened this with the idea of nearly decomposable systems. Complex systems often have strong interactions inside local clusters and weaker interactions between clusters. That is why departments work. Not because departments are magically good, but because they create local zones where detail can be processed without flooding the whole body.

Hierarchy here does not only mean domination. It also means compression. Lower layers handle dense local reality. Higher layers receive summaries, set constraints, allocate resources, and resolve conflicts that local layers cannot solve alone.

Who Figured This Out?

No single person figured it out.

The pattern was discovered by survival, long before theorists named it. Ancient states needed scribes because grain, labor, taxes, land, law, contracts, supplies, and military campaigns could not be held in memory. Ancient Egypt had provinces, officials, stores, manpower organization, legal supervision, and writing as an administrative medium. Mesopotamian scribes handled contracts, land measurement, taxes, supplies, military messages, and calculations.

Then modern theorists named different pieces:

The pattern came first. The theories are later mirrors.

The Ten-Organ Map

This is the clearest crystallization:

These are not always separate departments. In small systems, one person or organ can carry multiple functions. In larger systems, one function can become a department, then a ministry, then an ecosystem.

The important move is to separate function from job title. “Treasury,” “finance,” “metabolism,” “budgeting,” and “capacity planning” are different field names for a resource function. “Court,” “HR investigation,” “family mediation,” “checkpoint,” and “approval gate” are different field names for judgment and dispute resolution.

The Same Anatomy Across Bodies

The map becomes powerful when it is placed across scale.

The vertical atlas

The first map is vertical: what counts as a “main body” at each level, and what kind of order keeps it coherent. This is not saying every level has government in the human sense. Below social life, “governance” becomes metaphorical: physical law, self-organization, homeostasis, selection, signaling, and feedback.

The vertical atlas gives the scale. The organ map gives the horizontal anatomy inside any body that is complex enough to need internal differentiation.

The analogy should stay functional, not literal. A cell does not have a finance department. But it does face resource intake, energy production, boundary maintenance, production, repair, transport, memory, and adaptation.

The Internal Jargon Is Different, The Organ Is Similar

Different fields hide the same organ under different names. That is one reason the pattern is hard to see at first.

This is why the phrase “domain masters” lands. A domain master is not merely a specialist. It is a custodian of one slice of reality.

What Existing Frameworks See

The ten-organ map is not floating alone. It overlaps with several established frameworks, each cutting the world differently.

None of these exactly equals the ten-organ map.Since version 2.0 (February 2024), the NIST Cybersecurity Framework has six functions: Govern was added to identify, protect, detect, respond and recover. That is good. The ten-organ map is a translation layer: it lets you compare government, family, company, cell, and software without being trapped inside one discipline’s jargon.

The Recursive Turn

Here is where the idea becomes almost fractal.

The whole has organs. But each organ, once complex enough, becomes a whole. Then it needs organs too.

Take “resource management” in a country. It starts as one function: treasury, tax, budget, allocation. But the treasury itself needs:

• Direction: fiscal policy.
• Resources: its own budget and staff.
• Operations: tax collection, payments, accounting.
• Memory: ledgers, historical accounts, forecasts.
• Defense: anti-fraud, audit, anti-corruption.
• Growth: investment strategy, economic modeling.
• Care/repair: relief, stabilization, bailouts.
• Communication: budget statements, reporting.
• Judgment: tax appeals, internal review.
• Learning: forecasting, policy revision.

Same for a military, a school, a hospital, a family caregiving role, a software platform team, or a mitochondrion inside a cell. A part becomes a whole whenever its internal complexity requires self-maintenance.

• Main body
  • Direction
  • Resources
    • Resource body
      • Direction inside resources
      • Operations inside resources
      • Memory inside resources
      • Defense inside resources
      • Learning inside resources
  • Operations
  • Memory
  • Defense
  • Repair

This is why governments have ministries, ministries have departments, departments have divisions, divisions have teams, teams have roles, roles have routines, and routines have checklists.

The clean principle:

Any part that becomes complex enough to maintain itself becomes a mini-whole.

Organization Is Not A Shape, It Is A Survival Grammar

The breakthrough is to stop asking only about shape.

A pyramid, network, council, hierarchy, circle, market, family, school, and ministry are shapes. But underneath shape is a grammar of survival:

1. boundary
2. identity
3. energy
4. work
5. memory
6. protection
7. repair
8. communication
9. judgment
10. adaptation

The shape can change while the grammar remains.

A startup may combine finance, HR, legal, ops, and product inside three people. A mature company separates them. A household handles them informally. A state codifies them in law. A cell embodies them chemically. A software platform encodes them in logs, services, alerts, backups, auth, deployment pipelines, and postmortems.

The point is not that every system needs the same org chart. The point is that every durable body has to answer the same questions somehow.

The dangerous failure is not always “we lack a department.” Sometimes the department exists but the function is not real. A company may have a risk team that cannot block risk. A family may talk often but not communicate truth. A state may have archives but manipulate records. A software team may have postmortems but never learn.

Diagnostic Use: Finding The Missing Organ

The map becomes practical when used as a diagnostic instrument.

This is the practical line:

1. Do not ask only “who is in charge?”
2. Ask “which function is not being carried?”

What This Is Not

This is not a final law of reality.

The ten functions are a strong working lens. The boundaries can shift:

• Defense and judgment can overlap.
• Operations and repair can overlap.
• Growth and learning can overlap.
• Communication may be the substrate for all social functions.
• Direction may be explicit in human organizations but implicit in natural systems as survival, selection, homeostasis, or attractors.

The deeper principle is probably this:

Any complex body must preserve coherence across time while exchanging energy, information, matter, and pressure with its environment.

The ten functions are a human-readable anatomy for that deeper principle.

Further Reading

Read in this order if the curiosity keeps pulling.

How To Use The Map

1. Keep the ten-organ map as a working ontology, not a doctrine.
2. Test it against many bodies: household, company, school, state, software system, organism, cell.
3. For each body, map who or what carries each function.
4. Mark functions as real, nominal, overloaded, missing, duplicated, or blocked.
5. Pay special attention to memory, judgment, repair, and learning. These are often where systems pretend to be mature but silently rot.
6. Use VSM when you need a more formal recursive model.
7. Use Mintzberg/Galbraith/Nadler when you need practical organization design language.
8. Use Ostrom when the problem is shared resources and local governance.
9. Use NIST/ITIL-style thinking when the problem is operational risk and recovery.
10. Keep one caution alive: organization reduces chaos, but it can also create dead bureaucracy if its organs serve themselves instead of the body.

Sources

Appendix

Method

This piece distills a long conversation into a research question, then maps it against established lenses: Ashby’s law of requisite variety, Simon’s architecture of complexity, Koestler’s holons, Beer’s Viable System Model, Weberian bureaucracy, Parsons’ AGIL, Mintzberg’s organization parts, Galbraith/Leavitt/Nadler-Tushman alignment models, Ostrom’s commons governance, biological compartmentalization, autopoiesis, free energy, and NIST cybersecurity functions. The aim is not to prove a final universal taxonomy. The aim is to crystallize that curiosity into a map that is intellectually grounded and practically usable.

Searches covered: Stafford Beer viable system model; Ashby requisite variety; Simon architecture of complexity; Weber bureaucracy; Maturana/Varela autopoiesis; Friston free energy principle; Mintzberg organization design; Galbraith Star Model; McKinsey 7S; Leavitt Diamond; Nadler-Tushman congruence; Ostrom commons governance; Parsons AGIL; Koestler holon/holarchy; UN COFOG; OECD Centres of Government; Ancient Egypt and Mesopotamian scribes; NIST Cybersecurity Framework; cell organelles and biological organization. Sources were used as conceptual anchors rather than as a statistical dataset. This piece intentionally preserves the original framing while grounding it in established theory.

Related

• AI, From the Atoms Up links here; shares security, governance, organisations
• Business Shape Morphology links here; shares evolution, organisations
• The Law of the Jungle shares governance, government
• Red Trees shares governance
• From A to B shares evolution