> 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/committee-overview/committees/committee-glossary-of-terms.md). # Committee Glossary of Terms {% hint style="danger" %} **ARCHIVED** This page has been archived. It's content might be outdated. {% endhint %} | **Term** | **Definition** | | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Committee Maturity Framework | This is the framework used to assess the maturity of the Committees. More information can be found [here](https://intersect.gitbook.io/committee-development/)​ | | Committee Working Group (different to Technical Working Group) | Aligned to a Committee (or possibly a function). Informal, short term working groups which have a defined purpose and agreed output. Anyone can request to be part of a Committee Working Group.More information on our Committee Working Groups can be found [here](https://app.gitbook.com/o/Prbm1mtkwSsGWSvG1Bfd/s/YvFHlnOutCDX87s6u04z/intersect-committee-development/glossary-of-terms-committee-related#committee-working-groups)​ | | Subject Interest Groups | Aligned to a Committee (or possibly a function). Set up to provide space to allow group think relating to a particular subject of interested and a mechanism to feed this into Intersect and engage with the wider membership. The term of these groups will be agreed between the group lead and associated committee / function. | | Technical Working Group (different to Committee Working Group) | Technical Working Groups which are aligned to Cardano Infrastructure development, they were previously also known as Product Working Groups. Depending on with scope and requirements the time duration, team size and other resources will be defined when the working group is established.More information on Technical Working Groups can be found [here](https://intersect.gitbook.io/intersect-working-groups/)​ | | Committee Chair | The Chair of the committee, the responsibilities of this role can be found within the committee spaces | | Committee Contributor. | A person that has been invited or given permission to attend a committee meeting to provide a contribution (SME advice, report update, group think input, working group update etc) | | Committee Observer | An Intersect member who has been invited or given permission to observe a committee meeting, this individual does not have committee voting rights | | Committee Seated Member | Intersect Members which have been voted onto a specific committee, details on how to apply to a committee can be found within the committee spaces or by emailing the committee. This individual will have committee voting rights | | Committee Secretary | The Secretary of the committee, the responsibilities of this role can be found within the committee spaces | --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://committees.docs.intersectmbo.org/committee-overview/committees/committee-glossary-of-terms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.