> For the complete documentation index, see [llms.txt](https://playnet.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playnet.gitbook.io/docs/welcome.md).

# Welcome

### Playnet experiments with games/organizations that enable societal flourishing

**Network ➡ Playnet**\
**Less Work ➡️ More Play**\
**That’s the politics**

Playnet is not an organization in the traditional sense, but a living laboratory for reimagining human coordination, creativity, and the realization of potential.&#x20;

We are an experimental platform that seeks to transform how humans play, work, and create together - moving beyond rigid structures towards dynamic, adaptive networks of mutual empowerment.

Playnetarians experiment at various scales, from micro-scale interactions to local-impact initiatives, city-wide engagements, and interplaynetary collaborations, fostering a global network (a playnet) of creative play and cooperation.

**We’re/Were/Are/You’re/Will,Be Open Sourcing the Matrix**


---

# 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://playnet.gitbook.io/docs/welcome.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.
