# Zoned Holon

A **Zoned Holon** is a holon whose membership is stratified into concentric zones, each representing a different depth of commitment, responsibility, and access. Instead of a binary "member / not a member," participation is graded: people move inward as they take on more responsibility, and outward as their involvement shifts.

This pattern mirrors how living communities actually work—there is rarely a single class of "member"—and it lets a holon recognize many forms of contribution without forcing everyone into the same role.

## How zones work

Each zone defines:

* A **depth of participation** (from anchoring operations to occasional support).
* The **rights** that come with that depth (governance voting, treasury access, ability to onboard others, etc.).
* The **expectations** placed on members at that level.
* The **value weight** their contributions carry in the holon's [value equation](/getting-started/funding-flow.md).

Movement between zones is not promotion in the traditional sense. It is a continuous adjustment: as someone takes on more, they move toward the core; as they step back, they move outward. The system is designed so that **the right people end up in the right roles** without rigid status hierarchies.

## Example zone structure

A common four-zone configuration:

* **Zone 1 — Core Stewards.** Anchor operational roles. Ensure stability and continuity. Hold the highest level of trust and treasury access.
* **Zone 2 — Active Contributors.** Regularly participate in governance, projects, and development. Carry most of the day-to-day work.
* **Zone 3 — Ambassadors.** Represent the holon outward—spread the work, attract new members, build relationships with adjacent holons.
* **Zone 4 — Supporters.** Provide financial or resource-based contributions without active participation. Still recognized as part of the holon.

Each participant moves between zones based on their involvement and the value they bring. The system dynamically adjusts, ensuring meaningful participation is incentivized at every depth.

## Zoned Holon vs. Relational Zones

These two concepts share a name but operate at different scales—worth keeping straight:

* A **Zoned Holon** describes the **internal** membership structure of a single holon (Zone 1 → Zone 4 as above).
* **Relational Zones**, in the [funding flow](/getting-started/funding-flow.md) primitives, describe **bilateral economic relationships between separate holons**—e.g., "I'll share my space if you share your expertise." They live on the external side of the [Splitter Holon](/software/holons-types-flavor/splitter-holon.md) dial.

A holon can be Zoned internally **and** participate in Relational Zones externally; the two compose cleanly.

## When to use a Zoned Holon

Choose this flavor when:

* Contributions arrive in very different forms (time, money, advocacy, advisory) and you want each to be visible and valued.
* The holon needs a clear path for deeper involvement without creating gate-kept hierarchies.
* Governance rights, treasury access, or value-equation weighting should scale with depth of participation rather than being uniform.

Zoned structure pairs well with an [Appreciative Holon](/software/holons-types-flavor/appreciative-holon.md) value system, since appreciations can both signal and trigger movement between zones.


---

# Agent Instructions: 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/software/holons-types-flavor/zoned-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.
