> For the complete documentation index, see [llms.txt](https://docs.hydra-voting.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hydra-voting.intersectmbo.org/overview/intersect-hydra-voting-tool.md).

# Intersect hydra voting tool

Documentation and guides for Intersect’s Hydra-voting tool. Powered by Ekklesia.

## What this tool is

Intersect’s Hydra-voting is the tool Intersect uses for all those processes that require alignment before a governance action. This tool is powered by Ekklesia.

## Documentation sections

<table data-view="cards"><thead><tr><th>Section</th><th>Description</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Voting events guide</strong></td><td>Coming soon</td><td></td></tr><tr><td><strong>Budget process guides</strong></td><td>Guides for budget cycles, and budget-related voting.</td><td><a href="/budget-process/budget-proposal-submission.md">Budget process 2026</a></td></tr><tr><td><strong>CC elections guides</strong></td><td>Coming soon</td><td></td></tr></tbody></table>

## Who built and maintains it

* **Intersect** operates the governance process and maintains this documentation.
* **Ekklesia** provides the underlying voting tooling and platform capabilities.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hydra-voting.intersectmbo.org/overview/intersect-hydra-voting-tool.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.