> For the complete documentation index, see [llms.txt](https://committees.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://committees.docs.intersectmbo.org/intersect-budget-committee/about/how-to-join-or-contact-us.md).

# How to Join or Contact Us?

Criteria for joining the Budget Committee

* Strong understanding of the Cardano Ecosystem and blockchain technology.
* Experience in financial planning, budgeting, or treasury management.
* Commitment to transparency, collaboration, and community-driven processes.
* Ability to dedicate time for regular meetings and committee work.
* Excellent communication and analytical skills.
* Demonstrated integrity and commitment to Cardano's values.

Please join us on the Intersect Discord server in the #budget-committee-area channel.

## Telegram

For informational releases only, join the Intersect Cardano Budget Committee Announcement channel: <https://t.me/IntersectCBCAnnounce>&#x20;

For Community Engagement join the Intersect Cardano Budget Committee Channel: <https://t.me/IntersectCBC>&#x20;

## X

On X please follow and interact with <https://x.com/IntersectCBC>&#x20;

## YouTube

On YouTube please follow and interact with <https://www.youtube.com/@IntersectCBC>&#x20;

You can also email us at <budget-committee@intersectmbo.org>


---

# 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://committees.docs.intersectmbo.org/intersect-budget-committee/about/how-to-join-or-contact-us.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.