> 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. 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://playnet.gitbook.io/docs/welcome.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.