> 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/july-2026-vote-to-update-bylaws/faqs.md).

# FAQs

<details>

<summary><strong>Why is Intersect updating the ByLaws now?</strong></summary>

The current ByLaws were created more than two years ago. Since then, Wyoming Law has evolved, Intersect governance processes have been created, Board structures have changed. The Intersect Board, the body accountable to keep the ByLaws updated, requested a legal review to improve clarity, remain compliant and align ByLaws to operational reality.

</details>

<details>

<summary><strong>Are these changes creating a new governance model?</strong></summary>

No. The updates primarily clarify and formalize governance practices that are already in use while improving legal alignment and operational clarity.

</details>

<details>

<summary><strong>Will my membership change because of these updates?</strong></summary>

No. The proposed updates do not change the purpose of membership or the overall role members play within Intersect.

</details>

<details>

<summary><strong>How do I vote?</strong></summary>

Once voting opens on 15 July 2026, log in to the Member Area. From the left-hand navigation menu, select Voting Events, then click Active Voting Events. You'll find the ByLaws vote there, where you can cast your vote.

</details>

<details>

<summary><strong>What happens if the proposal is approved?</strong></summary>

If the proposal receives the required level of support, the updated ByLaws will become the official governing document of Intersect.

</details>

<details>

<summary><strong>What happens if the proposal is not approved?</strong></summary>

If the proposal does not receive the required approval threshold, the existing ByLaws will remain in effect until further action is taken.

</details>

<details>

<summary><strong>Were members consulted during the review?</strong></summary>

Yes, while the board is responsible for maintaining the Bylaws, feedback was sought from the Intersect Steering Committee during the review process. Ultimately the proposed update must be approved by eligible members through a vote.

</details>


---

# 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/july-2026-vote-to-update-bylaws/faqs.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.