> 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-steering-committee/working-group/working-groups/working-group-meeting-notes/2026/february-12-2026.md).

# February 12 2026

### Attendees: 

| Name                                                 | Attendance | Role                                  |
| ---------------------------------------------------- | ---------- | ------------------------------------- |
| [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes        | WG Lead/Secretary                     |
| Thiago Nunes                                         | Yes        | Intersect Member                      |
| Vaibhav S                                            | Yes        | Intersect Member                      |
| Maureen Wepngong                                     | No         | DRep                                  |
| Terence McCutcheon                                   | Yes        | Intersect                             |
| Lorenzo Bruno                                        | Yes        | Head of Product Curation at Intersect |
| Jose Miguel De Gamboa                                | No         | ISC Voting Member                     |
| Randy                                                | Yes        | <p><br></p>                           |
| Wilco van de Burgwal                                 | Yes        | <p><br></p>                           |
| Pedro Lucas                                          | Yes        | <p><br></p>                           |
| Gnobudy John                                         | Yes        | <p><br></p>                           |

Recording: [Intersect Governance WG Weekly - 2026/02/12 14:59 CET - Recording](https://drive.google.com/open?id=1IqczuO6E7f-zfdEsLLkgVhzeYk4c8vb6\&authuser=0)

Transcript: [Intersect Governance WG Weekly - 2026/02/12 14:59 CET - Transcript](https://docs.google.com/document/d/1eE7oFHnuEptAWa_d3N2uDPafDYZRviD8GIxTUEw0AJU/edit?usp=drive_web\&ouid=116259958284654754795)

### Agenda

* Committee Members Role & Responsibilities
* Extending Committee term

### Decisions/Actions

| Discussion Point             | Notes                                                                                                                                                                                                                         | Actions: Responsible / Note                                                                                                   |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Two-Year Term Implementation | The ISC and Board have approved the two-year term extension starting with the April 2024 elections. Mitigation strategies for "power consolidation" include showing mandatory participation data for all applicants.          | Lorenzo Bruno to update the application form to include historical participation data (voting history, committee attendance). |
| Committee Member Roles       | Brainstormed the core duties: providing expertise, attending at least 75-85% of meetings, and acting as a bridge to the community. Debate continued on whether members should "execute" or strictly "steer."                  | Lorenzo Bruno to draft a formal "Committee Member Responsibilities" document based on Miro board notes.                       |
| Chair & Vice Chair Roles     | The Chair is the primary lead and ISC representative, while the Vice Chair ensures "situational awareness" to step in at any time. Chairs are responsible for preventing "external capture" and prioritizing strategic goals. | Working Group to refine the "Signatory" and "Escalation" protocols for Chairs within the new policy draft.                    |
| Election Cadence             | Gintama suggested shifting the October election to January/February to avoid "governance fatigue" during the Cardano Summit and the budget cycle.                                                                             | Working Group to evaluate a long-term plan to shift election windows for better community engagement.                         |
| Accountability & Dismissal   | Wilco raised concerns about "ghost members" receiving rewards without contributing. The group noted that four committees have already utilized the version 1 dismissal policy.                                                | Terence McCutcheon to update the secretary tracker to verify dismissal data across all committees by the next meeting.        |
| Bylaw Updates                | With more member-elected seats now on the Board, the Intersect bylaws require a formal update and a subsequent member ratification vote.                                                                                      | <p><br></p>                                                                                                                   |


---

# 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-steering-committee/working-group/working-groups/working-group-meeting-notes/2026/february-12-2026.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.