> 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-committee-minutes-30th-april-2026.md).
# Civics Committee Minutes 30th April 2026
#### Attendees
| Name | Attendance | Role | Voting Seat (Y/N) | Election Term |
| ----------------- | ---------- | --------- | ----------------- | ------------- |
| Nicolas Cerny | Yes | Chair | Y | April 2026 |
| Larisa Mcfarlane | Yes | Secretary | N | N/A |
| Megan Dyamond | No | Member | Y | October 2026 |
| Thomas Lindseth | No | Intersect | N | N/A |
| Ken-Erik Ølmheim | Yes | Member | Y | April 2026 |
| Simon Fleck | Yes | Member | Y | October 2026 |
| Ian Hartwell | Yes | Member | Y | October 2026 |
| Musa Ridwan Itopa | No | Member | Y | October 2026 |
| Dzubang Mermoz | Yes | Member | Y | April 2026 |
| Randy | Yes | Member | Y | April 2026 |
#### Sources
[CIVICS Committee (Intersect) Meeting - 2026/04/30 13:59 BST - Recording](https://drive.google.com/file/d/1a9xcMIkNRgIxt9yppqhz0bWkAoL55GCB/view?usp=sharing)
[CIVICS Committee (Intersect) Meeting - 2026/04/30 13:59 BST - Transcript](https://docs.google.com/document/d/15tWGuuW6oFzzTDFWYGaTke6O2s5jCi1l1ZCEW6KS8ZM/edit?usp=sharing)
#### Agenda Items
* Update from the Intersect Steering Committee (ISC)
* Committee Elections Status
* Service Rewards Policy Evaluation
* Constitutional Amendment Process (CAP) Working Group Update
* Governance Incentives Working Group Charter Ratification
* Civics Committee Budget Proposal Refinement and Vote
#### Decisions/Actions
**Decisions Made**
* Charter Ratification: The committee officially ratified the charter for the Governance Incentives Working Group. The purpose was clarified to include providing recommendations to the Cardano community through the Civics committee.
* Budget Strategy Change: The committee decided to strategically reduce the quantity of flagship workshops from nine to six (one per continent) to improve the proposal's chances of approval by DReps.
* Workshop Coordination: Language will be added to the budget proposal stating an intention to minimize costs by coordinating workshop logistics with other Intersect committees where possible.
* Budget Approval: The committee voted unanimously (6-0) to approve version 6 of the budget proposal for submission to the Hydra voting tool for community feedback.
**Action Items**
* Civics Committee Members: Cast votes for the next committee election in the members' portal by tomorrow, May 1, at 12:00 PM UTC.
* Civics Committee Members: Continue testing the CAP tool on various devices and report any bugs directly to the working group.
* S (Seomon): Coordinate with TL to verify which wallets have successfully implemented the optional governance incentives grant.
* LM & NC: Clean up the finalized budget document and submit it to the Hydra voting tool.
#### Topic Notes
| Topic | Discussion | Notes |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| 1. ISC & Budget Overview | The Intersect main budget was submitted via the Hydra tool and features three extensive work packages. | Board members attended the ISC meeting to provide oversight on the submission. |
| 2. Service Rewards | The IC is reassessing committee stipends, specifically the original intent of anchoring them to USD (e.g., $500) versus ADA. | Current rewards are guaranteed through the end of June 2026. |
| 3. CAP Working Group | TL continues to refine the tool based on daily bug reports. A new historical summary of the amendment process has been added to the portal. | Members are encouraged to "break the tool" using dummy amendments to find edge cases. |
| 4. Governance Incentives | The group's scope is defined as consolidating existing research and efforts rather than solving the problem in perpetuity. | Milestone 1 involves mapping existing incentive research, with future milestones to be added only after reassessment. |
| 5. Wallet Integration | A discussion occurred regarding the low adoption rate of the governance incentive grant by wallet builders. | Only the Eternl wallet has successfully completed and claimed the grant to date. |
| 6. Civics Budget Proposal | The proposal was restructured to prioritize governance tooling and education infrastructure over workshops. | The committee agreed that workshops are non-profit; any unspent funds from the 20,000 ADA allocation per event will be returned to the treasury. |
| 7. Infrastructure Lessons | The recent downtime of the GovTool (Gv tool) was cited as a stark reminder that unfunded governance infrastructure lacks accountability and maintenance. | This event underscored the necessity of the committee's budget for sustaining governance layers. |
---
# 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-committee-minutes-30th-april-2026.md?ask=&goal=
```
`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.