> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/parallel-society-playbook.md). # Parallel Society Playbook The Parallel Society Playbook is a growing collection of practical knowledge from Circles around the world, each entry filed under the civil society issue bucket it belongs to. Its purpose is simple: when a Circle figures out how to solve a concrete, winnable civil society issue, we want other Circles to be able to learn from that experience and adapt it locally. Rather than every Circle having to start from scratch, we can turn local organising experience into shared knowledge. That is what carries the work past one city. A solution proven by one Circle can be run by fifty, and an issue solved in fifty places stops being a single campaign and becomes an institution people can rely on. Circles already share the same stack. This is where they share what they learn building on it. One entry covers one issue: the problem, why it was winnable, what the Circle did, who it worked with, what worked, what failed, and which parts another Circle could reuse. Every entry comes from a Circle that ran the campaign, written by the people who ran it. Entries live on the [Logos Forum](https://forum.logos.co/) under the \`playbook\` tag, in the open, where any Circle can read them and reply to the Circle that wrote them. Together, the issues we solve form the basis of a global parallel society. --- # 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://circles.logos.co/parallel-society-playbook.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.