Field Note: [fn.2 ] Organization vs Structure - The Story of Change Without Change

[fn.2 ] Bitcoin STRUCTURE has changed by factors of millions since 2009—in hashrate, price, transactions, users—yet remains "Bitcoin" because its ORGANIZATION is unchanged. In this article a comphrensive discussion on how ORGANIZATION defines identity and how STRUCTURE enables operation.
Field Note: [fn.2 ] Organization vs Structure - The Story of Change Without Change
id: fn.2 
title: "Organization vs Structure" 
parent: step.02 extends: step.03 
connects: fn.1, step.04, step.05, step.06 
status: complete contains: fn.2.c, fn.2.d 
source: "Maturana & Varela, Luhmann"

fn.2 — Organization vs Structure

The Bridge

In step.02** **, an introduction to autopoiesis was made. Specifically, the ideas and concepts of self-production and self-organizing - a new definition of LIFE. Not just a description of life, but an articulation of the process for the organization of the living.

In step.03** **, the exploration continues with how systems maintain identity through change. The keyword here being COHERENCE and VIABILITY.

fn.2 bridges these through a crucial distinction: Organization (what makes a system this kind of system) vs Structure (the actual state at any moment).

This distinction explains how Bitcoin can change massively—in hashrate, price, adoption, code—while remaining “Bitcoin.”

Part I: The Original Distinction (Maturana & Varela)

Definitions from Autopoiesis Theory

From my early experiential education thesis, citing Bopry (1999):

Organization: “The set of relationships among an entity’s components that characterize the system as belonging to a particular class (i.e. bacterium, tree, dog…).”

Structure: “Refers to the physical properties within the system and to the roles of the components of the system.”

The Key Insight

Organization is invariant. Change the organization, and you no longer have the same kind of system. A dog with a different organization is no longer a dog.

Structure is variant. A dog can grow, age, lose a leg, gain weight—its structure changes constantly—but it remains a dog as long as its organization persists.

The Relation Between Them

Aspect Organization Structure
Nature Pattern of relations Physical properties, roles
Stability Invariant (defines identity) Variant (changes constantly)
Level Abstract (class membership) Concrete (particular instance)
Change Changes organization = changes kind Changes structure = same system

Part II: Luhmann’s Modification

Structure as Expectation

Luhmann shifts the concept of structure from physical properties to expectations:

“Having clarified the concept of structure and identified structures for social systems as structures of expectation, we can now turn to the question of what structures have a chance of being chosen and proving their worth in the course of evolution.” — Luhmann, Social Systems

For social systems, structure isn’t physical—it’s what participants expect. Structures are the patterns of expectation that enable ongoing operation.

Structure in Service of Autopoiesis

Luhmann argues that structure must be understood in relation to autopoietic self-reproduction:

“The basis of this discussion changes if one understands structures from the viewpoint of the necessity for autopoietic self-reproduction. This can allow highly individualized dovetailing, which makes it easier quickly to discover modes of connective behavior.”

Structure serves autopoiesis. The system selects structures that enable its own continuation.

Structure Loses “Central Position”

Importantly, Luhmann argues that structure is not the essence:

“The concept of structure loses its central position, although it remains indispensable. No systems theorist would deny that complex systems form structures and that they could not exist without them. But the concept of structure is now ordered within a pluralistic arrangement of different concepts without claiming preeminence among them.”

Translation: Structure matters, but it’s not what defines the system. What defines the system is its organization—the pattern that makes it this kind of system.


Part III: Bitcoin’s Organization

What Makes Bitcoin “Bitcoin”?

Bitcoin’s organization consists of the invariant rules that define it as a particular kind of system:

Organizational Element Description Invariant?
21 million cap Maximum supply ever YES
Proof-of-work consensus Miners compete for block rewards YES
~10 minute block time Difficulty adjustment target YES
Halving schedule Subsidy halves every 210,000 blocks YES
UTXO model Unspent transaction outputs YES
Longest chain rule Most accumulated work wins YES
Script validation Transaction validity rules YES (mostly)

These organizational elements define Bitcoin as “Bitcoin.” Change any of them fundamentally, and you have a different system.

The Fork Test

When Bitcoin forks, we can see organization vs structure clearly:

Fork What Changed Organization or Structure? Result
Segwit Block weight calculation Structure (optimization) Still Bitcoin
BCH Block size limit (1MB → 8MB+) Organization (capacity rules) Different system
BSV Further block size changes Organization Different system
Difficulty adjustment Every 2016 blocks Structure (parameters) Same system

Incentives and constraints matter, Segwit changed how data is structured, but preserved the organization. BCH changed the organizational rules about block capacity—by rewriting the constraints themselves it became a different kind of system, even though it shares history.


Part IV: Bitcoin’s Structure

What Changes Constantly

Bitcoin’s structure is everything that varies while organization persists:

Structural Element Description Variant?
UTXO set Current unspent outputs YES (every block)
Hashrate Total network mining power YES (constantly)
Difficulty Current mining difficulty YES (every 2016 blocks)
Mempool Unconfirmed transactions YES (constantly)
Node count Active network nodes YES (constantly)
Price Market valuation YES (constantly)
Block height Current chain length YES (every ~10 min)
Code version Most common client software YES (with releases)

The structure changes with every block, every transaction, every new node. Yet Bitcoin remains Bitcoin.

Structural Change Is Not Identity Change

From 2009 to 2025:

Aspect 2009 2025 Change
Hashrate ~1 MH/s ~500 EH/s 500,000,000,000,000x
Price ~$0 ~$100,000
Transactions/day ~10 ~500,000+ 50,000x
UTXO set size ~50 ~150,000,000 3,000,000x
Block height 0 ~870,000 870,000 blocks

The structure is completely different. The organization is the same. Bitcoin is still Bitcoin.


Part V: The Luhmann-Maturana Integration

Two Perspectives, One Insight

Theorist Organization Means Structure Means
Maturana Pattern defining class membership Physical properties and roles
Luhmann Operational pattern (autopoiesis) Expectations enabling continuation

Both agree: Organization defines identity. Structure enables operation.

Applied to Bitcoin

Level Maturana Framing Luhmann Framing Bitcoin Example
Organization What makes it “this kind” Operational pattern 21M cap, PoW, consensus rules
Structure Physical properties Expectations UTXO set, hashrate, mempool
Identity Class membership System continuity “Bitcoin” vs “not Bitcoin”

The Autopoiesis Connection

Why does organization persist?

Because the system’s autopoietic operations reproduce the organization. Every block validates according to the rules. Every transaction confirms the rules. The rules produce the transactions that confirm the rules.

Luhmann: “Structure serves autopoiesis.”

The organizational rules aren’t external constraints imposed on Bitcoin. They ARE Bitcoin. Bitcoin produces itself by applying these rules, and in applying them, reproduces them.


Part VI: Structural Coupling and Structural Determination

From the EE Thesis

Structural Coupling:

“Systems can change along two different paths—internal or external. Externally, a living system interacts with the environment through recurrent interactions, each of which triggers structural changes in the system.”

Structural Determination:

“Systems are structure-determined. According to Maturana, behavior in living systems is determined by the systems own structure. The lower oxygen levels only act as triggering device (called a perturbation). Interactions with the environment are not instructive.”

Applied to Bitcoin

Structural Coupling: Bitcoin is structurally coupled to:

  • Mining hardware industry

  • Energy markets

  • Financial systems

  • Regulatory environments

  • User behavior

Each coupling triggers structural changes (hashrate, fees, adoption) without changing organization.

Structural Determination: Bitcoin’s responses are determined by its own structure, not by external events:

External Event Perturbation Bitcoin’s Response (Structure-Determined)
China bans mining Hashrate drops Difficulty adjusts down
ETF approved Demand increases Price rises, fees increase
Halving occurs Subsidy decreases Miners adapt or exit
Exchange hacked Users scared Some move to self-custody

The environment does not instruct Bitcoin. It perturbs. Bitcoin responds according to its own organizational logic.


Part VII: Why This Matters for Bitcoin Education

The Common Confusion

People often confuse structural changes with organizational changes:

Claim Confuses Structure With Organization?
“Bitcoin is dying” (hashrate drops) YES — structural change
“Bitcoin is different now” (price up) YES — structural change
“Bitcoin has changed” (Segwit) MAYBE — was it organization or structure?
“BCH is Bitcoin” (fork) NO — organization changed, different system

The Identity Question

When someone asks “Is this still Bitcoin?”, the answer depends on organization:

Scenario Organization Changed? Still Bitcoin?
Hashrate drops 90% NO YES
Price drops 90% NO YES
Segwit activates NO YES
Lightning Network NO (Layer 2) YES (L1 unchanged)
21M cap removed YES NO
PoW → PoS YES NO

The Fork Decision Framework

When evaluating a proposed change:

  1. Does it change organization or structure?

  2. If organization: This creates a different system

  3. If structure: This is variation within the same system

This is why “block size wars” were existential—the debate was about organization (what kind of system Bitcoin is), not just structure (how big blocks should be).


Part VIII: Connecting to the Framework

How Organization/Structure Maps to Other Steps

Step Connection
step.01 (Definition) Your definition reveals whether you see organization or structure
step.02 (Autopoiesis) Organization enables autopoiesis; structure is produced by it
step.04 (Closure) Operational closure maintains organization
step.05 (Coupling) Structural coupling changes structure, not organization
step.06 (Perturbation) Environment perturbs structure; organization determines response
step.11 (Emergence) Organization is designed; emergent properties are structural

The Richmond Connection

Richmond Process Relates to…
Process 1-2 (Training) Depositing structure (information)
Process 3-5 (Teaching) Building organizational understanding

You can TELL someone about Bitcoin’s structure (current price, hashrate). You cannot TELL them its organization—they must construct that understanding themselves.

The Glasersfeld Connection

Glasersfeld Concept Organization/Structure Mapping
Scheme Cognitive organization
Assimilation Fitting new info into existing organization
Accommodation Changing cognitive organization
Perturbation Structural disruption triggering potential accommodation

The “rattle-spoon dilemma” is about cognitive organization. When the spoon doesn’t rattle, the infant must either preserve organization (reject spoon) or change organization (new scheme). Bitcoin education faces the same challenge.


Part IX: The Debate Continues

Two Positions on Bitcoin’s Organization

Position A (Maturana/Mingers):

  • Organization must be biological

  • Bitcoin has “organization-like” properties but not true organization

  • It’s a coordination technology with organizational closure

Position B (Luhmann/RC):

  • Organization can be operational (communications)

  • Bitcoin’s consensus rules ARE its organization

  • Transactions reproduce the rules that produce transactions = autopoietic organization

Both Positions Agree

Regardless of which position you take:

  1. Organization is invariant — change it, change the system

  2. Structure is variant — changes constantly, same system

  3. Identity comes from organization — not from structure

  4. Structure serves organization — enables its continuation


Summary

The Core Distinction

Aspect Organization Structure
What it is Pattern defining identity Properties at any moment
Stability Invariant Variant
Change Creates different system Same system, different state
Bitcoin example 21M cap, PoW, consensus UTXO set, hashrate, price

The Key Insight

Bitcoin maintains identity through organizational invariance ( i.e. preservation) despite massive structural change.

From 2009 to 2025, Bitcoin’s structure has changed by factors of millions and billions. Its organization has remained the same. That’s why it’s still Bitcoin.

The Educational Implication

You can describe Bitcoin’s structure (facts, numbers, states). You cannot transfer Bitcoin’s organization (understanding must be constructed). This is why:

  • Explaining price doesn’t create understanding

  • Showing hashrate charts doesn’t orange-pill

  • Describing transactions doesn’t convey the system

The organization must be constructed from within the learner. Structure is information. Organization is understanding.


Navigation

← Back to \[[step.02|Autopoiesis](https://primal.net/a/naddr1qvzqqqr4gupzphnw7gaw5q2dpxqmzhm7al5pky5hmfvcy07urp2czqyh78s4y0c5qqwxzat5dacx76t9wd5hxttp94jx2ets94ehjmn5dpjhx6tnhsz20d) ] ↑ Up to \[[fn.1|You Can't Copy a Process](

) ] → Forward to [\[step.03|Structure\]](https://primal.net/a/naddr1qvzqqqr4gupzphnw7gaw5q2dpxqmzhm7al5pky5hmfvcy07urp2czqyh78s4y0c5qy88wumn8ghj7mn0wvhxcmmv9uq3xamnwvaz7tmsw4e8qmr9wpskwtn9wvhsqsrrd3hhxety946x7ttfdeehgun4vd6xjmmw94hhqetw946x7ttnw3ex2umn943xjarrda5kuuedv9h8g6txwfskw6tvv5kkgetnd9nku3neczd)

Branch into the fn.2 Constellation

Branch Topic Status
\[\[fn.2.c]] | The Block Size Wars | *Planned* | | \[\[fn.2.d]] | Portfolio as Perturbation Machine | *Planned* | | fn.2.a | The Fork Test | *Planned* | | fn.2.b | Structural Coupling in Bitcoin | *Planned* | ## Cross-References * See also: \[[fn.1|You Can't Copy a Process]( ) ] — Why organization can't be transferred * See also: \[[fn.0.f|Glasersfeld's Scheme Theory\]](https://primal.net/a/naddr1qvzqqqr4gupzphnw7gaw5q2dpxqmzhm7al5pky5hmfvcy07urp2czqyh78s4y0c5qqyrzvpsvgerye3he3a2dy) — Cognitive organization
  • See also: [[step.04|Closure]] — Operational closure maintains organization

  • See also: [[step.06|Perturbation]] — Structure changes, organization determines response


fn.2 — Organization vs Structure — December 2025 “The concept of structure loses its central position, although it remains indispensable… it is now ordered within a pluralistic arrangement of different concepts without claiming preeminence among them.” — Niklas Luhmann, Social Systems


Write a comment
No comments yet.