> 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/communication-strategies-how-do-we-make-sense-of-the-world/the-member-intro-assembly.md).

# The Member Intro Assembly

## Structure

When a DHO/DAO officially launches and each subsequent year there is a recorded call where every member (as possible) of the DHO/DAO gives a 60-90 second introduction to who they are and what role(s) they fill. \
\
With this model every new member can go back and watch the latest recording and get a quick intro to each person - direct from that person (opposed to through someone else's lens which is what often happens). 

### Examples include:

* Gathering each year on the organizations birthday for all members to say hello, share stories and build community. 

### Suggested When:

For remote and decentralised teams that don't share the same workplace.

### Known Pitfalls:

* Requires coordination to find a time that's suitable for all members.

#### Authored by Rieki Cordon, Hypha DHO


---

# 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/communication-strategies-how-do-we-make-sense-of-the-world/the-member-intro-assembly.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.