> 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-civics-committee/meeting-minutes/2026-civics-meeting-minutes/civics-meeting-minutes-26th-feb-2026.md).

# Civics Meeting Minutes 26th Feb 2026

## Attendees:&#x20;

| Name              | Attendance | Role      | Voting Seat (Y/N) | Election Term |
| ----------------- | ---------- | --------- | ----------------- | ------------- |
| Nicolas Cerny,    | Apologies  | Chair     | Y                 | April 2026    |
| Larisa Mcfarlane  | Apologies  | Secretary | N                 | N/A           |
| Thomas Lindseth   | Yes        | Intersect | N                 | N/A           |
| Ken-Erik O        | Yes        | Member    | Y                 | April 2026    |
| Nana Safo         | Yes        | Member    | Y                 | April 2026    |
| Alex Seregin      | No         | Member    | Y                 | April 2026    |
| Randy             | Yes        | Member    | Y                 | April 2026    |
| Dzubang Mermoz    | No         | Member    | Y                 | April 2026    |
| Ian Hartwell      | Yes        | Member    | Y                 | October 2026  |
| Megan Dyamond     | Yes        | Member    | Y                 | October 2026  |
| Musa Ridwan Itopa | Yes        | Member    | Y                 | October 2026  |
| Simon Fleck       | No         | Member    | Y                 | October 2026  |

Transcript: [CIVICS Committee (Intersect) Meeting - 2026/02/26 12:55 GMT - Notes by Gemini](https://docs.google.com/document/d/1wRv4gHB_cnFo9IZjPg9WUhg0MdXveoxu47rhoEP4rhw/edit?tab=t.5fb2qcf56lxj)

Recording: [CIVICS Committee (Intersect) Meeting - 2026/02/26 12:55 GMT - Recording](https://drive.google.com/file/d/1oI69lYuiwVjnRXWtHf4d172romzgPkzF/view)

## Agenda 26 Feb 2026

• CAP WG, Gov Health WG, Gov Ed WG Updates

• Budget Workstream

• Committee Elections & Terms

### Decisions/Actions

#### The Civics Committee meeting on Feb 26, 2026, focused heavily on the 2026/2027 budget proposal, inter-committee coordination on governance actions, and the upcoming Constitutional Committee (CC) election timeline.

#### Decisions Made

* #### Budget Presentation: The committee decided they are ready to present a high-level overview of their budget initiatives to the Steering Committee (ISC) next Monday, focusing on the "what" and "why" rather than granular figures.
* #### Committee Coordination (Situation Awareness): The committee agreed to take an active role in "assisting in awareness" regarding upcoming governance actions (hard forks, parameter updates, etc.) to prevent overlapping or clashing proposals, while respecting the permissionless nature of the ecosystem.
* #### Budget Benchmarking: The committee will look to the Product Committee’s 2024/2025 workshop budget (approx. 750k ADA) as a reference for cost-effective community outreach.
* #### Stipend Process: New tax forms for 2026 are required for all members to receive stipends. A manual test with select members is occurring this week before a full rollout.

#### Action Items

* #### Budget Document Cleanup: KØ and MD to finalize the "Civics Budget 2026/2027" document, ensuring the 1 million ADA soft cap is maintained before the Monday ISC meeting. Historical figures and resources requested to assist in this exercise.
* #### Resource Database: N and RR to collaborate with KØ to set up a public-facing database (likely via GitHub) for educational resources by Tuesday, March 3.
* #### Cross-Committee Sync: N to connect with Lucas (observer) to exchange resources on governance tooling and existing documentation.
* #### Election Publicity: TL to share the finalized CC election timeline in the internal Civics chat; committee members to prepare for outreach starting in May.
* #### Governance Action Tracking: KØ to add a standing item to the weekly agenda to discuss known upcoming governance actions (e.g., Plutus cost models, hard forks) to maintain "situation awareness."

<table data-header-hidden><thead><tr><th width="137"></th><th width="380"></th><th></th></tr></thead><tbody><tr><td>Topic</td><td>Discussion</td><td>Notes</td></tr><tr><td>1. Budget Cycle 2026/2027</td><td>Simo (Steering Committee) joined to explain the budget workflow. Each committee must provide a high-level list of initiatives to the executive team next week to check for alignment and duplication.</td><td>Focus is on "what" we want to fund, not granular costs yet. A Mirror board will be used to present these to the board.</td></tr><tr><td>2. Budget Initiatives (5.1 &#x26; 5.3)</td><td>MD and KØ consolidated DRep participation ideas into a regional workshop strategy (approx. 400k ADA). RR discussed building on "Beyond MVG" research to create an updated governance measurement standard.</td><td>The goal is to hit 70% DRep participation. Workshops should ideally be side-events at existing Intersect gatherings to save costs.</td></tr><tr><td>3. Constitutional Amendment (CAP)</td><td>MD provided an elevator pitch for introductory workshops (3-5 in-person, 2 online) to teach the community how to use the new amendment process.</td><td>The process is dependent on community buy-in. MD noted the recent "brute forced" changes by Utah as a reason why a structured process is vital.</td></tr><tr><td>4. CC Election Timeline</td><td>TL confirmed the finalized dates for the 2026 Constitutional Committee elections. Registration opens May 1st; voting occurs from mid-June to mid-July.</td><td>Timeline was adjusted to avoid conflicts with other ecosystem events. Info action to be submitted for board approval.</td></tr><tr><td>5. Committee Coordination</td><td>KØ and IH discussed the "clashing" of governance actions (e.g., parameter updates vs. hard forks). IH noted that while permissionless, the committee should assist in "situation awareness."</td><td>The committee will act as an information hub to alert the community of potential proposal overlaps and technical timelines.</td></tr><tr><td>6. CAP Working Group Update</td><td>MD reported that the CAP amendment form is nearly complete. The group is moving on to defining the scope and roles for "Editors" in the first phase.</td><td>A pilot test of the CAP process may be run alongside an upcoming Technical Steering Committee (TSC) proposal.</td></tr><tr><td>7. Education Working Group</td><td>N (returned from Nairobi) and RR are reviewing educational resources against a set framework. They plan to build a public database (GitHub) for these materials.</td><td>N will sync with KØ on the technical setup of the database; first batch of resources expected by next Tuesday.</td></tr><tr><td>8. Member Stipends</td><td>Simo confirmed that the automated stipend system is ready for testing. Members will need to fill out a 2026 tax form and provide a wallet address.</td><td>Testing with a few members starts this week; full announcement expected by Friday or next Monday.</td></tr><tr><td>9. Steering Committee Priorities</td><td>KØ updated the group on SC talks regarding Catalyst administration, treasury returns, and the role of Intersect in node release management.</td><td>Administrative roles for Catalyst funding are being clarified at the board level.</td></tr><tr><td>10. Governance Awareness</td><td>The meeting concluded with a brief mention of current on-chain actions, including Emurgo’s treasury withdrawal request for 206k ADA.</td><td>KØ encouraged members to review the proposal on-chain.</td></tr></tbody></table>

<br>


---

# 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/intersect-civics-committee/meeting-minutes/2026-civics-meeting-minutes/civics-meeting-minutes-26th-feb-2026.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.
