> For the complete documentation index, see [llms.txt](https://docs.holons.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holons.io/getting-started/what-is-a-holon.md).

# What is a Holon?

The word **holon** comes from Greek: *holos* (whole) + *on* (part). A holon is a thing that is **simultaneously a whole and a part of something larger**. Your body is a holon: it is a whole organism, and it is part of a family, a community, an ecosystem. A team is a holon: a whole working unit, and a part of an organization.

The Holons protocol takes this idea and makes it usable as a coordination tool. Every group—family, team, cooperative, neighborhood, region—can run as a holon: self-governing internally, and composable with other holons externally.

This page is the short version. For the full architecture see [Funding Flow](/getting-started/funding-flow.md); for definitions of every recurring term see the [Glossary](/getting-started/glossary.md).

## The four ideas that make a holon work

A working holon needs to answer four questions. Each has a primitive in the protocol.

### 1. What holds it together? — the **membrane**

A holon has a [membrane](/getting-started/glossary.md#membrane): a flexible boundary that defines who is in, what the holon is for, and what it values. Membranes are semi-permeable—people, resources, and information cross in and out under conditions the holon sets for itself. The membrane is what gives the holon an identity distinct from its surroundings.

### 2. What is valued inside? — the **value equation**

Each holon defines its own [value equation](/getting-started/glossary.md#value-equation): a formula that converts contributions (hours, outcomes, appreciations, relationship-building) into points, and points into shares of whatever the holon distributes. Two holons can run identical software and produce very different cultures, simply by tuning the weights.

A common starting equation:

```
Points = (Hours × Hour_Weight) +
         (Appreciations × Appreciation_Weight) +
         (Outcomes_Delivered × Outcome_Weight)

Share  = Points_Individual / Points_Total
```

### 3. How do resources move? — **splitters and thresholds**

When resources flow into a holon, they are routed by primitives:

* A [Splitter](/getting-started/glossary.md#splitter) divides incoming flow between destinations—often between internal contributors and external ecosystem partners, with a single dial controlling the balance.
* A [Threshold Bucket](/getting-started/glossary.md#threshold-bucket) accumulates resources until a minimum need is met, then sends overflow to a downstream holon or federation pool.

Together these primitives make it possible to say: "fund what we need first, then share the surplus with the people who help us thrive."

### 4. How does it connect to others? — **federation**

Holons [federate](/getting-started/glossary.md#federation) by declaring trust relationships with other holons. A federation can be as light as "we share appreciation data" or as committed as "we share a mutual-aid treasury." Once federated, value can flow across holon boundaries under the rules each holon defines for itself. This is how a coffee co-op, a regional fund, and a bioregional alliance can act as one network without giving up their autonomy.

## A concrete picture

Imagine a community garden running as a holon:

1. The garden is a Telegram group. Members add the [HolonsBot](/software/holonsbot.md) and declare a purpose ("steward this land, feed the neighborhood").
2. Members use `/appreciate` to recognize each other's work—weeding, watering, hosting workshops. Appreciations accumulate as a public record.
3. The garden runs a **value equation** that weights appreciations heavily, hours moderately, and outcomes (harvests, workshops delivered) the most.
4. A small grant arrives. A **splitter** sends 70% to active contributors (proportional to points) and 30% into an ecosystem pool shared with three nearby gardens.
5. The four gardens have **federated**: when any one of them has surplus, it overflows into the shared pool, which redistributes to whichever garden currently needs it most.

Nothing here required a central authority. The rules are explicit, the record is public, and every holon retained its autonomy.

## Where to go next

* **Want the architectural depth?** Read [Funding Flow](/getting-started/funding-flow.md) — the full whitepaper on contracts, distribution mechanisms, and federation.
* **Want a specific shape of holon?** See [Holon types (flavor)](/software/holons-types-flavor.md) for composable patterns: [Splitter](/software/holons-types-flavor/splitter-holon.md), [Managed](/software/holons-types-flavor/managed-holon.md), [Zoned](/software/holons-types-flavor/zoned-holon.md), [Appreciative](/software/holons-types-flavor/appreciative-holon.md).
* **Want to set one up?** Start with [Setting up your holonic organization](/daos/setting-up-your-holonic-organization.md).
* **Want a specific use case?** Browse the [Application Areas](https://github.com/liminalvillage/holonsdocs/blob/main/application-areas/README.md) — non-profits, bioregional regeneration, mutual aid, family management, and more.
* **Stuck on a term?** The [Glossary](/getting-started/glossary.md) is the single source of truth for vocabulary.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.holons.io/getting-started/what-is-a-holon.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.