# MCC - Working Group and Interest Group Process Design

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

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

## Purpose

This working group seeks to provide clear and concise definitions and standards for the various types of groups that are formally recognized as part of the Intersect processes.

## Related committee

Civics Committee\
Membership and Community Committee\
Open Source Committee\
Technical Steering Committee 

## Working group lead

Mark B

## Working group members

Matthew C (Membership and Community Committee)

Michael M (Civics Committee)

Alex

Mark B (Membership and Community Committee)

Phil L 

Lloyd D (Civics Committee)

Adam D (Open Source Committee)

Christian (Open Source Office - Intersect)

Tex (Open Source Office - Intersect)

Matt (Technical Steering Committee)

## Working group objective / desired outcome

Develop process, definition, and framework for Intersect groups.  This will start from proposal through triage, review to closure.

## Collaboration channels 

* [#WG-working-group-and-interest-group-design](https://discord.com/channels/1136727663583698984/1235113257312849950)

## Outputs

* [ ] [**General Framework**](/groups-overview/working-groups/working-group-and-interest-group-process-design/general-framework.md) - A document containing the output from this working group after it has passed through the working group members for review, feedback, and acceptance. Currently still a work-in-progress and subject to frequent changes and modifications.


---

# Agent Instructions: 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:

```
GET https://groups.docs.intersectmbo.org/groups-overview/working-groups/working-group-and-interest-group-process-design.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.