> For the complete documentation index, see [llms.txt](https://opensourcecommittee.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://opensourcecommittee.docs.intersectmbo.org/working-groups/working-group-calendar.md).

# Working Group Calendar

Cadences for Intersect working groups and technical working groups. Last Updated: 2 July, 2025

<table><thead><tr><th width="249.5390625">Group Name</th><th width="119.984375">Day</th><th width="123.578125">Time</th><th>Cadence</th></tr></thead><tbody><tr><td>Dev Ex 1</td><td>Wednesday</td><td>7am UTC</td><td>Bi-Weekly</td></tr><tr><td>Dev Ex 2</td><td>Thursday</td><td>5pm UTC</td><td>Bi-Weekly</td></tr><tr><td>Tooling WG</td><td>Friday</td><td>12pn UTC</td><td>Weekly</td></tr><tr><td>Network TWG</td><td>Monday</td><td>3pm UTC</td><td>Every 6 Weeks</td></tr><tr><td>Enterprise &#x26; Government Adoption</td><td>Tuesday</td><td>8am UTC</td><td>Bi-Weekly</td></tr><tr><td>Cardano Research</td><td>Tuesday</td><td>3pm UTC</td><td>First Tuesday</td></tr><tr><td>GovTool</td><td>Wednesday</td><td>3pm UTC</td><td>Bi-Weekly</td></tr><tr><td>Governance Support</td><td>Thursday</td><td>3pm UTC</td><td>Every 3 Weeks</td></tr><tr><td>Intersect Governance</td><td>Thursday</td><td>2pm UTC</td><td>Weekly</td></tr><tr><td>Plutus TWG</td><td>Tuesday</td><td>2pm UTC</td><td>Bi-Weekly</td></tr><tr><td>Commercialization</td><td>Thursday</td><td>3pm UTC</td><td>Bi-Weekly</td></tr><tr><td>Layer 2 (formerly Hydra) TWG</td><td>Wednesday</td><td>12pm UTC</td><td>Bi-Weekly</td></tr><tr><td>API/CLI TWG</td><td>Wednesday</td><td>3pm UTC</td><td>3rd Wednesday</td></tr><tr><td>Partner Chains TWG</td><td>Thursday</td><td>4:30pm UTC</td><td>Every 4 Weeks</td></tr><tr><td>Tech Support TWG</td><td>Thursday</td><td>4pm UTC</td><td>Bi-Weekly</td></tr></tbody></table>


---

# 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://opensourcecommittee.docs.intersectmbo.org/working-groups/working-group-calendar.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.