> For the complete documentation index, see [llms.txt](https://docs.civiform.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.civiform.us/governance-and-management/governance.md). # Governance CiviForm is free, open-source software that was built by the City of Seattle with support from Google.org Fellows. It is developed and maintained by its community of users and contributors, including civic entities, Google.org Fellows, and Exygy. Each government deploys and manages their own instance of CiviForm using the shared codebase. Participants in the CiviForm project are expected to abide by the shared Code of Conduct. Through the collective development and maintenance of best-in-class software, CiviForm aims to expand access to government services to those who need them most. The following docs describe the processes and principles by which CiviForm is collectively developed and maintained: * [Roles, Committees, & Responsibilities](/governance-and-management/governance/roles-committees-and-responsibilities.md) * [Governance Processes](/governance-and-management/governance/governance-processes.md) * [Development Principles](/governance-and-management/governance/development-principles.md) * [Communication Guidelines](/governance-and-management/governance/communication.md) --- # 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.civiform.us/governance-and-management/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.