Functional Anatomy of Systems

How complex bodies turn chaos into named responsibility

Author

Research

Published

May 16, 2026

WindowConceptual deep dive, sources checked 2026-05-16

SourcesCybernetics, systems theory, organization theory, governance, biology, IT risk

MethodConversation distillation + web research + framework synthesis

AuthorWorkbench research-report

Executive summary

The curiosity began with a simple but heavy observation: families, schools, companies, governments, bodies, cells, and software systems all seem to invent roles. The names change, but the functions keep coming back. A state gets ministries, courts, tax offices, archives, police, schools, hospitals, and planning bodies. A company gets finance, operations, legal, HR, product, marketing, security, support, and strategy. A cell gets a membrane, nucleus, mitochondria, ribosomes, transport machinery, degradation machinery, and signaling.

The pattern is not that everything is literally a government. The pattern is that any complex body must remain coherent while facing more reality than one center can hold. It therefore develops an internal anatomy: direction, resources, operations, memory, defense, growth, repair, communication, judgment, and learning. These are not sacred final categories. They are a strong working map for seeing how chaos becomes governable.

Tip

The recommendation, in one line. Treat the ten functions as a diagnostic anatomy: when a body feels chaotic, ask which organ is missing, overloaded, lying, cut off, or pretending to be another organ.

Headline numbers

Candidate organs

Aiming, resourcing, operating, remembering, defending, growing, repairing, coordinating, judging, learning.

VSM functions

Stafford Beer's viable-system lens: operations, coordination, control, intelligence, identity.

Parsons imperatives

AGIL: adaptation, goal attainment, integration, latency/pattern maintenance.

Ostrom design principles

Commons governance adds boundaries, monitoring, sanctions, conflict resolution, and nested enterprises.

Methodology

This report distills the 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 the user’s curiosity into a map that is intellectually grounded and practically usable.

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:

too much reality
too many disturbances
too much memory required
too many conflicts
too many tasks
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.

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.

Pressure	Organizational answer
Too many details	Local domains
Too many disturbances	Specialized response capacity
Too many decisions	Decision rights
Too many memories	Records and ledgers
Too many exceptions	Escalation paths
Too much drift	Standards, audits, reviews

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.

Note

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:

Thinker / tradition	What they named	Why it matters here
Max Weber	Bureaucracy, office, rules, rational-legal authority	Role-stabilized administration
W. Ross Ashby	Requisite variety	Complexity must be matched by regulatory capacity
Herbert Simon	Near decomposability, hierarchy, bounded rationality	Parts-within-parts make complexity manageable
Arthur Koestler	Holons and holarchy	A body can be both whole and part
Stafford Beer	Viable System Model	Minimal recursive functions for organizational survival
Talcott Parsons	AGIL functional imperatives	Social systems must solve recurring functional problems
Henry Mintzberg	Strategic apex, operating core, middle line, technostructure, support staff	Organizations have recurring anatomical parts
Elinor Ostrom	Commons governance, monitoring, conflict resolution, nested enterprises	Governance can be local, distributed, and durable
Maturana and Varela	Autopoiesis	Living systems produce and maintain themselves
NIST / IT operations	Identify, protect, detect, respond, recover	Modern systems formalize defensive and recovery organs

The pattern came first. The theories are later mirrors.

The Ten-Organ Map

This is the clearest crystallization of the conversation:

Function	Question it answers	Failure mode if missing
Direction / purpose	Where are we going and why?	Drift, contradiction, wasted motion
Resource management	What do we have and how is it allocated?	Starvation, waste, hidden obligations
Operations / maintenance	How does the body keep running?	Plans never become reality
Memory / records	What happened and what is true?	Repeated mistakes, disputes over reality
Defense / risk	What can harm us?	Exposure, intrusion, preventable loss
Growth / expansion	How do we become more capable?	Stagnation, shrinking optionality
Care / repair	How do we heal damage?	Burnout, accumulated breakage
Communication	How do parts coordinate?	Desynchronization, duplicated work
Judgment / dispute resolution	How are conflicts decided?	Rot, factionalism, unresolved ambiguity
Learning / adaptation	How do we update from experience?	Fragility, obsolete rules

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.

Scale	Main body	Ordering mechanism	What it teaches
Cosmic	Universe	Physical law, fields, entropy, symmetry breaking	Order can exist without intention
Galactic	Galaxies, star systems	Gravity, orbital dynamics, energy flows	Stable wholes form from repeated constraints
Planetary	Planet, climate, geology	Cycles, feedback loops, thresholds	Large bodies self-regulate until thresholds break
Biospheric	Ecosystems, species	Evolution, niches, food webs, selection	Survival distributes roles without a central planner
Civilizational	Civilizations, world systems	Trade, war, law, language, religion, technology	Meaning and infrastructure scale coordination
Governmental	States, regions, cities	Law, administration, taxation, public records	Offices turn territory into governable reality
Institutional	Companies, schools, hospitals	Departments, roles, metrics, routines	Work becomes stable through named responsibility
Household	Family, kin network	Care, norms, budgeting, memory, conflict habits	Informal governance still carries real functions
Individual	Person	Attention, identity, habits, emotion, memory	The self is also an internal organization problem
Organismic	Body	Nervous, immune, endocrine, circulatory systems	Survival needs fast coordination and repair
Cellular	Cell	Membrane, organelles, signaling, DNA	Compartmentalized function appears at micro-scale
Molecular	Molecules, atoms	Bonds, charges, fields, quantum constraints	At this level, “role” becomes physical relation

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

Function	Country	Company	School	Family	Individual	Cell	Software / infra
Direction	Constitution, cabinet, strategy	Board, CEO, strategy	Principal, mission	Family values, future plan	Identity, goals	DNA and regulatory networks	Roadmap, architecture principles
Resources	Treasury, tax, budget	Finance, procurement	Bursar, funding	Household budget	Money, time, energy	ATP, nutrients	Cloud budget, capacity
Operations	Ministries, civil service	Operating core, delivery	Teaching, timetable	Meals, errands, chores	Routines, execution	Ribosomes, ER/Golgi	Deploys, jobs, runbooks
Memory	Archives, registry, statistics	Accounting, CRM, knowledge base	Student records	Documents, stories	Memory, notes	DNA, epigenetic state	Logs, database, git
Defense	Military, police, health security	Security, legal, risk	Safeguarding, discipline	Boundaries, locks	Threat detection	Membrane, peroxisomes	Auth, monitoring, backups
Growth	Economic development, education	Sales, R&D, marketing	Curriculum, enrichment	Career support, child development	Skill building	Replication, differentiation	Scaling, product growth
Care	Hospitals, welfare, maintenance	HR, support, wellness	Counseling, nurse	Caregiving	Sleep, recovery	Repair pathways, lysosomes	Incident response, rollback
Communication	Diplomacy, media, reporting	Meetings, dashboards, chat	Parent letters, assemblies	Conversations	Language, nervous system	Signaling, vesicles	APIs, queues, alerts
Judgment	Courts, appeals, ombudsman	Legal, HR, governance	Discipline board	Conflict resolution	Conscience, decision rules	Checkpoints, error correction	Approvals, policy checks
Learning	Research, education, audit	Retros, analytics, R&D	Exams, feedback	Lessons learned	Reflection, habit change	Adaptation, selection	Postmortems, tests

Warning

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.

Distilled name	Government jargon	Company jargon	Biology jargon	Software / ops jargon
Direction	Policy, mandate, constitution	Strategy, OKRs, mission	Genetic regulation, set points	Architecture, roadmap, SLOs
Resources	Treasury, appropriation, procurement	Finance, budget, allocation	Metabolism, ATP, nutrient uptake	Capacity, cost, quotas
Operations	Civil service, delivery agency	Operating model, value stream	Protein synthesis, transport	Jobs, deploys, services
Memory	Records, census, archive	Ledger, CRM, data warehouse	DNA, epigenetic marks	Logs, database, git history
Defense	Security, policing, risk office	Legal, compliance, security	Membrane, immune system, detox	Auth, firewall, backup, DR
Growth	Development, education, industry	Marketing, sales, R&D	Differentiation, reproduction	Scaling, adoption, product loops
Care	Health, welfare, maintenance	Support, HR, customer success	Repair, degradation, autophagy	Incident response, rollback
Communication	Diplomacy, public comms, reports	Meetings, dashboards, comms	Signaling pathways	APIs, queues, alerts
Judgment	Courts, tribunals, appeals	HR, legal, governance board	Checkpoints, error correction	Approvals, policy engine
Learning	Audit, research, schools	Retros, experimentation, analytics	Plasticity, adaptation, selection	Tests, postmortems, observability

This is why the user’s phrasing “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.

Framework	Its core lens	What it contributes
Ashby’s law	Regulation must match variety	Why delegation is necessary
Simon’s complexity	Parts-within-parts, near decomposability	Why nested bodies reduce complexity
Koestler’s holon	Whole and part at once	Why recursion feels natural
Beer’s VSM	Viable systems need recursive functions	A strong formal ancestor of the organ map
Weber bureaucracy	Offices, rules, hierarchy, records	How modern administration stabilizes roles
Parsons AGIL	Adaptation, goals, integration, pattern maintenance	A compact functional ancestor
Mintzberg	Strategic apex, operating core, middle line, technostructure, support staff	A concrete organization anatomy
Galbraith Star	Strategy, structure, process, rewards, people	Alignment matters as much as existence
Nadler-Tushman	Work, people, formal and informal organization must fit	Misfit creates execution failure
Ostrom commons	Boundaries, monitoring, sanctions, conflict resolution, nested enterprises	Governance can be distributed
NIST CSF	Identify, protect, detect, respond, recover	Modern risk organs made explicit

None of these exactly equals the ten-organ map. That is good. The ten-organ map is a translation layer: it lets the user 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.

flowchart TD
  A[Main body] --> B[Direction]
  A --> C[Resources]
  A --> D[Operations]
  A --> E[Memory]
  A --> F[Defense]
  A --> G[Repair]
  C --> C1[Resource body]
  C1 --> C2[Direction inside resources]
  C1 --> C3[Operations inside resources]
  C1 --> C4[Memory inside resources]
  C1 --> C5[Defense inside resources]
  C1 --> C6[Learning inside resources]

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.

The Climax: Organization Is Not A Shape, It Is A Survival Grammar

The user’s breakthrough was 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:

boundary
identity
energy
work
memory
protection
repair
communication
judgment
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.

Important

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.

Symptom	Likely organ issue
Everyone is busy but nothing compounds	Direction or learning is weak
Money/time disappears without explanation	Resource management or memory is weak
Problems repeat every month	Learning is not connected to operations
People argue over what happened	Memory/records are weak or distrusted
Everyone waits for one person	Local operations lack decision rights
Teams duplicate work	Communication and records are weak
Small failures become emergencies	Defense, repair, or monitoring is weak
Rules exist but nobody follows them	Judgment lacks authority or legitimacy
The system cannot change	Growth/adaptation is weak
The system changes constantly but never stabilizes	Direction, memory, or operations are weak

This is the practical line:

Do not ask only "who is in charge?"
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.

Reading Path

Read in this order if the curiosity keeps pulling.

Stage	Book	Why it belongs
Start here	Donella Meadows, Thinking in Systems	Friendly opening into feedback, stocks, flows, leverage points
Complexity backbone	Herbert Simon, The Sciences of the Artificial	Hierarchy, near decomposability, bounded rationality
Control problem	W. Ross Ashby, An Introduction to Cybernetics	Requisite variety and regulation
Organizational viability	Stafford Beer, Diagnosing the System for Organizations	Practical entry into the Viable System Model
Formal anatomy	Henry Mintzberg, Structure in Fives	Strategic apex, operating core, middle line, technostructure, support staff
Governance without overcentralization	Elinor Ostrom, Governing the Commons	Boundaries, monitoring, conflict resolution, nested institutions
Administration and offices	Max Weber, Economy and Society selections	Bureaucracy, authority, offices, rationalization
Organizational behavior	March and Simon, Organizations	Bounded rationality, routines, decision behavior
Whole-parts	Arthur Koestler, The Ghost in the Machine	Holons and holarchy
General systems	Ludwig von Bertalanffy, General System Theory	Historical foundation of systems science
Living systems	Maturana and Varela, Autopoiesis and Cognition	Self-producing living organization
Advanced social theory	Niklas Luhmann, Social Systems	Society as differentiated communication systems
Practical design	Jay Galbraith, Designing Organizations	Strategy, structure, process, rewards, people
Reliability and sensemaking	Karl Weick, Managing the Unexpected	High-reliability organizations, sensemaking
Cautionary counterweight	James C. Scott, Seeing Like a State	Why top-down legibility can erase local reality

Recommendations

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

Source Map

Source	Link	Used for
Ashby, requisite variety	panarchy.org/ashby	Why regulation needs matching complexity
Simon, architecture of complexity	MIT PDF	Near decomposability, nested systems
Koestler, holon	panarchy.org/koestler	Whole-part recursion
Beer, VSM	Umbrex VSM	Recursive viable functions
Mintzberg, Structure in 5’s	INFORMS	Basic organization parts
Weber, bureaucracy	Britannica and SEP	Offices, rules, rationalization
Egypt administration	Britannica	Ancient administrative organs
COFOG	UN Statistics	Government functions as formal categories
Centre of Government	OECD	Central coordination and monitoring
Parsons AGIL	Sociology Plus	Functional imperatives
Ostrom	Overview	Commons governance and nested institutions
Cell organelles	Biology LibreTexts	Biological compartmentalization
Autopoiesis	University of Chile record	Living systems as self-producing organization
Free Energy Principle	Entropy/MDPI	Biological systems resisting disorder
NIST CSF	NIST blog and Quick Start PDF	Identify/protect/detect/respond/recover

Methodology notes

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. The report intentionally preserves the user’s framing while grounding it in established theory.