> 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-3rd-march-2026.md).

# Civics Meeting Minutes 3rd March 2026

## Attendees:&#x20;

| Name              | Attendance | Role      | Voting Seat (Y/N) | Election Term |
| ----------------- | ---------- | --------- | ----------------- | ------------- |
| Nicolas Cerny,    | Yes        | Chair     | Y                 | April 2026    |
| Larisa Mcfarlane  | Yes        | 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      | Yes        | Member    | Y                 | April 2026    |
| Randy             | Yes        | Member    | Y                 | April 2026    |
| Dzubang Mermoz    | Yes        | 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       | Yes        | Member    | Y                 | October 2026  |

Transcript: [CIVICS Committee (Intersect) Meeting - 2026/03/05 12:51 GMT - Transcript](https://docs.google.com/document/d/1TUJ3oq1u6FO2r5WSx-Ltfh0w0EuBBUyiKkUfxn8PYU8/edit?usp=sharing)

Recording: [CIVICS Committee (Intersect) Meeting - 2026/03/05 12:51 GMT - Recording](https://drive.google.com/file/d/1tZ0hvChBSsYaQS7wCgkmMK-4rqnYsXL7/view?usp=sharing)

## Agenda 5 Mar 2026

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

• Budget Workstream

• Upcoming Committee Elections & Terms

#### Key Decisions

* #### Approval of CAP Phase 2 Form Fields: The committee unanimously approved (10/10) Section 5.2 of the Constitutional Amendment Process (CAP) document. This finalizes the input fields and the recommended consultation timelines (e.g., 60 days for substantive changes, 14 days for editorial).
* #### Approval of CC Election Input Fields: The committee approved the registration form fields for the upcoming Constitutional Committee (CC) elections. This included a last-minute addition by MD regarding candidates' familiarity with and interpretation of the Constitution.
* #### Election Cadence Change: It was decided to move to a once-yearly election cycle (every April). Current members whose terms expire in October will be asked to extend until April 2027 to align with this new cadence.
* #### Committee Size Cap: It was agreed to maintain a maximum of 10 paid voting members due to budget constraints.&#x20;
* #### Budget Info Action Support: The committee acknowledged and supported the submission of the Budget Process Info Action to the DREPs to gain a mandate for the 2026 budget framework.

#### ✅ Action Items

* #### NC: Transfer brainstorming document data to the ISC Miro board for the presentation on Monday morning.
* #### NC: Complete the recording for the committee election promotional video with LL.
* #### TL: Move internal CAP vote responses to the Civics folder and clean up formatting in the Phase 2 document.
* #### TL: Transmit the finalized CC election form fields to Elaia/Ecclesia for technical implementation.
* #### TL: Follow up with sitting CC members (East Cardano Council, Phil, Matthias) regarding their intent to run for re-election.
* #### LM: Publish the updated details and rules regarding the 5 elected seats versus potential appointed seats in the coming days.
* #### SR: Fix the "LettuceMeet" link and re-post the coordination link for the Governance Participation Working Group on Discord immediately.
* #### JM / NS: Join the next CAP Working Group call to discuss the procedural "edge case" of Treasury withdrawals during constitutional updates.
* #### All Members: Amplify Intersect election tweets and promotional materials via personal and committee social media accounts.

<table data-header-hidden><thead><tr><th width="129"></th><th width="436"></th><th></th></tr></thead><tbody><tr><td>Topic</td><td>Discussion</td><td>Notes</td></tr><tr><td>1. ISC &#x26; Budget Coordination</td><td>NC provided updates from the ISC regarding the budget framework exercise. The goal is to define responsibilities between committees and Intersect as an MBO before drafting official budget proposals.</td><td>NC to present the Civics committee’s current state and priorities at the next IC meeting.</td></tr><tr><td>2. Budget Process Info Action</td><td>NC (wearing Budget Committee hat) announced an upcoming "Info Action" to seek a mandate from DREPs for the budget process. This includes a 1,000 ADA donation for submissions to prevent spam and a 100,000 ADA minimum request.</td><td>Info Action is for process consensus, not immediate budget approval. Expected to launch before the epoch ends.</td></tr><tr><td>3. Committee Elections</td><td>LM confirmed the election timeline (Nomination phase starts March 30th). The committee will move to 5 elected seats, with the option to appoint up to 10 total members to maintain stability.</td><td>Terms will move to a two-year cadence starting in April to ensure a once-yearly election cycle.</td></tr><tr><td>4. Member Retention &#x26; Outreach</td><td>AS expressed feelings of not bringing value; NC and LM reaffirmed the value of diverse opinions. LM noted Intersect is starting to tweet about elections to encourage applications.</td><td>Members are encouraged to amplify election posts. NC to record a promotional video with LL.</td></tr><tr><td>5. CAP Working Group Update</td><td>TL reported unanimous internal approval for Phase 2 fields and consultation times. Nine of 10 voting members responded. Results to be moved to the Civics folder.</td><td>Phase 2 document is available in the committee folder for review.</td></tr><tr><td>6. CAP Approval (Vote 1)</td><td>The committee voted on approving section 5.2 (CAP form fields) to finalize input fields and consultation timings (ranging from 14 to 60 days depending on the category).</td><td>Motion Passed</td></tr><tr><td>7. Constitutional Edge Cases</td><td>JM raised concerns regarding Treasury withdrawals caught in "no man's land" during constitutional updates. TL noted the process is for transparency, not individual legal vetting.</td><td>JM and NS invited to join upcoming CAP working group calls to discuss procedural safeguards.</td></tr><tr><td>8. Gov. Education Working Group</td><td>RR provided an update on the knowledge base/framework. Progress is being made on data collection, though categorization may need future adjustments as the process matures.</td><td>WG to continue aligning with data visualization efforts by NS.</td></tr><tr><td>9. CC Election Fields (Vote 2)</td><td>TL presented the registration fields for the Constitutional Committee (CC) elections. MD suggested adding fields for "familiarity with the constitution" and "interpretation."</td><td>Motion Passed: "Yes" (after MD’s amendments were included). TL to send.</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-3rd-march-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.
