> For the complete documentation index, see [llms.txt](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/introduction/coordination-layers-for-daos.md).

# Coordination Layers for DAOs

There are 3 major communication pieces for each organisation using a DAO/DHO structure to help members understand the organisation they are a part of.\
\
\&#xNAN;*This book contains a collection of strategies.*

![](/files/W35H4pVM8dGgaSlEHaiU)

## DAO & DHO Guides

#### **Low Adaptability**

*A condensed document* containing only the most foundational agreements that are the least likely to change. This document, such as a constitution, are often mandatory agreements that need to be well understood in order to become a member of a DAO/DHO.

*See the Hypha Guide (and feel free to copy) for an example.*

{% hint style="info" %}
*Like the official rules of a sport.*
{% endhint %}

### **Adaptability**

Changes are infrequent and usually have wide-ranging impacts across the whole organization. 

{% hint style="info" %}
Like who controls the treasury and how.
{% endhint %}

### **Governance (high)**

Changes require a vote from all members within a DAO/DHO to work.

## Hand Books

#### **Med Adaptability**

A single source of truth elaborating on the culture and processes of a DAO/DHO that new members are encouraged to read to gain an effective understanding. \
\&#xNAN;*See the Hypha Handbook (and feel free to copy) for an example.*

{% hint style="info" %}
Like the wide ranging diversity in culture, agreements, and styles of various teams playing a global sport.
{% endhint %}

### **Adaptability**

Changes are frequent (especially in the early days) as the community co-creates its unique culture.

{% hint style="info" %}
*Like the employee handbook of a company.*
{% endhint %}

### **Governance (med - high)**

Some organizations give editing authority to a role or circle within the DAO/DHO that holds this domain. Others require a vote from all members to update this document. 

## Strategies

#### **High Adaptability**

*A document c*ontaining a collection of strategies and formations that teams may use. \
**This book is one collection.** 

{% hint style="info" %}
Like the various plays that teams practice and use during a game. The best teams are always creating and experimenting with new plays and formations. 
{% endhint %}

### **Adaptability**

Changes most often as the community experiments with various org. strategies and matures into new patterns.

{% hint style="info" %}
*Like using Agile, Holacratic, Sociocratic, etc coordination methodologies within a department of a company.* 
{% endhint %}

### **Governance (low - high)**

Teams (circle, squad, etc) choose various strategies and how they decide which strategies to employ this would require only that team make the decision. However, when changing an organisation strategy (such as the authority pattern) it may require permission from the whole organization.


---

# 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, and the optional `goal` query parameter:

```
GET https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/introduction/coordination-layers-for-daos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.