> 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/groups-overview/working-groups/working-group-and-interest-group-process-design/general-framework.md).

# General Framework

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

Last Modified: 2024-05-27

{% hint style="info" %}
This document is still in a draft state and is subject to change. Presented here for the benefit of building in public on behalf of Intersect members.
{% endhint %}

## Intersect Group Types

| Group Type                                            | Docs & Comms                             | Membership                               | Purpose                                  |
| ----------------------------------------------------- | ---------------------------------------- | ---------------------------------------- | ---------------------------------------- |
| [**Committee**](#committee)                           | <mark style="color:blue;">Formal</mark>  | <mark style="color:blue;">Formal</mark>  | <mark style="color:blue;">Formal</mark>  |
| [**Sub-Committee**](#sub-committee)                   | <mark style="color:blue;">Formal</mark>  | <mark style="color:blue;">Formal</mark>  | <mark style="color:red;">Informal</mark> |
| [**Working Group**](#working-group)                   | <mark style="color:red;">Informal</mark> | <mark style="color:red;">Informal</mark> | <mark style="color:blue;">Formal</mark>  |
| [**Special Interest Group**](#special-interest-group) | <mark style="color:red;">Informal</mark> | <mark style="color:red;">Informal</mark> | <mark style="color:red;">Informal</mark> |
| [**(Core) Software Group**](#core-software-group)     | <mark style="color:blue;">Formal</mark>  | <mark style="color:blue;">Formal</mark>  | <mark style="color:blue;">Formal</mark>  |

{% hint style="info" %}
**Formal / Informal**

1. Formal - there are rules for it here.
2. Informal - there are no rules for it here.

For both the formal and informal status, the group is accountable for the decisions it makes to the group that it reports to.&#x20;

**Caveats to ‘Formal / Informal’**

1. Informal - if there are no rules for something, it doesn’t mean it’s unimportant what or how the decisions are made. It just means that its best to leave the quality of those decisions to the governance structure of the group and of Intersect.
2. Formal - if there are rules for something here, it doesn’t mean that there’s no room for deliberation, interpretation, judgment, and accountability. The rules here are as light as possible in order to be conducive to good decision-making and good work.
   {% endhint %}

### Committee

The groups that will always be necessary to administer Intersect’s general purposes

1. Administration of Intersect itself
2. Administration of the Cardano public good

Answers primarily to Intersect’s own internal hierarchy and needs.

### Sub-Committee

Any group that helps fulfill Intersect’s purposes in an area of ongoing work, that has a more dynamic definition than committees.

### Working Group

Any subgroup of a committee or subcommittee formed to carry out a specific task over a specific period of time, owned by one member of the parent group and accountable to it.

### Special Interest Group

A group for coordinating people who are interested in a specific topic in a low-stakes and exploratory way.&#x20;

1. This group type is governed by the MCC.&#x20;
2. It is intended to provide an easy way for small groups of members to coordinate without having to meet the standards of a formal subcommittee.

### (Core) Software Group

Definition pending\*


---

# 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/groups-overview/working-groups/working-group-and-interest-group-process-design/general-framework.md?ask=<question>&goal=<endgoal>
```

`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.