> 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-overview/jump-in-key-member-initiatives.md).
# Happening Now
This page gives quick access to current most important topics
Intersect Board Elections
In September, the **Intersect Board Elections** will take place — a vital opportunity for members to help select the individuals who will oversee Intersect’s strategic direction and ensure it remains aligned with its mission and community values. During this time members were able to elect **two board members** out of the seven that compose the Intersect Board.
{% hint style="info" icon="link" %}
**Useful Links**
* [September 2026 Board Elections](/intersect-knowledge-base/intersect-membership/intersect-voting-events/2026-intersect-elections/september-2026-board-elections.md)
{% endhint %}
Constitutional Committee Elections
* The CC Election process application will start on **May 8th at 9.45PM UTC**
{% hint style="warning" icon="calendar-days" %}
**Key dates**
* *Applications Submission*: May 8th, 9PM UTC to June 7th**,** 9.45PM UTC
* Candidate Promotion: June 7th, 9.45PM UTC to June 13th, 9.45PM UTC
* *Voting period*: June 13th, 9.45PM UTC to July 13th, 9.45PM UTC
Check the full timeline [here](/intersect-knowledge-base/cardano-facilitation-services/cardano-governance/2026-constitutional-committee-elections/cc-election-2026-timeline.md)
{% endhint %}
{% hint style="info" icon="link" %}
**Useful Links**
* [CC Election timeline](/intersect-knowledge-base/cardano-facilitation-services/cardano-governance/2026-constitutional-committee-elections/cc-election-2026-timeline.md)
* [Hydra-voting tool ](https://hydra-voting.intersectmbo.org/)(for application and voting)
{% endhint %}
## Happening Next
Intra-era hard fork
Intersect is hosting and facilitating the Hard Fork Working Group (HFWG) to coordinate and navigate ecosystem feedback and potential readiness before formal Cardano governance actions are raised for broader community consensus and approval. In essence, the working group follows much of the same processes and purpose as it did for the Chang and Plomin hardforks not so long ago.
{% hint style="info" %}
#### Keep informed
Join the dedicated Upgrade Discord channel at [#wg-hard-fork](https://discord.com/channels/1136727663583698984/1242097284619960411) (on the Intersect Discord server). This channel is monitored by the working group, with updates being shared and questions answered. Alternatively, you can reach out to
The hard fork working group currently meets every other week; see the shared [Luma Calendar](https://luma.com/calendar/cal-TMjYNpSY4huYYif). As progress continues, the meeting cadence will increase.
The [Cardano Upgrades GitBook](https://cardanoupgrades.docs.intersectmbo.org/) contains important hard fork context, working group policies, readiness tracking, and working group meeting minutes.
{% endhint %}
## Upcoming Governance Actions
No Governance Actions are planned for the short term
---
# 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.intersectmbo.org/intersect-knowledge-base/intersect-overview/jump-in-key-member-initiatives.md?ask=&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.