> For the complete documentation index, see [llms.txt](https://docs.beecapital.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beecapital.org/organization-and-governance/organization-and-governance.md). # Organization and governance BEE Capital DAO is in the process of changing its organizational structure and governance. We envision a structure that ensures sufficient efficiency and scalability, while maintaining creative freedom for its members. For more details on this vision, check out these resources. At a high-level, the BEE Capital DAO is governed by its community of BEE holders. All members are responsible for providing the vision and goals for BEE, and for interacting with its active contributors to help build this vision. Contributors are organized in the form of independent working groups called taskforces. **Organization structure** Contributors to BEE are organized in the form of taskforces. Each taskforce is an independent working group, with its own specified objective or vision. Taskforces have a large degree of autonomy in terms of how they spend their resources, how they hire and collaborate with contributors, what decisions they take to achieve their vision and so forth. Taskforces periodically report their progress to the DAO and request resources if needed. --- # 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://docs.beecapital.org/organization-and-governance/organization-and-governance.md?ask=&goal= ``` `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.