> For the complete documentation index, see [llms.txt](https://docs.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.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-voting-events/2026-intersect-elections/april-2025-committee-elections/april-2025-committee-election-results/statement-about-april-2026-election-results.md).

# Statement about April 2026 election results

## Executive Summary

Intersect ran committee elections in April 2026 across eight committees. As part of routine post-election review, our auditing identified an unusual concentration of voting activity that warranted closer examination. We commissioned an independent third party audit alongside our internal analysis. Both reached consistent conclusions.\
\
This statement sets out findings, and the decisions taken to preserve the integrity of the announced results, the path available to affected members, and how we intend to continue developing our membership and election processes. It is intended to be candid about what we observed while being careful not to attribute intent or wrongdoing to any individual on the basis of statistical patterns alone.

## Full Statement

{% file src="/files/Qoxqn1KzfM0StMORIesK" %}

## Third-Party Analysis performed by Dquadrant

{% file src="/files/Ut0hmKkosl3DwM49dkBs" %}


---

# 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://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-voting-events/2026-intersect-elections/april-2025-committee-elections/april-2025-committee-election-results/statement-about-april-2026-election-results.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 `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.