> 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-19th-march-2026.md).
# Civics Committee Minutes 19th March 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 |
| 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 | Yes | Member | Y | October 2026 |
## Sources
[CIVICS Committee (Intersect) Meeting - 2026/03/19 12:50 GMT - Notes by Gemini](https://docs.google.com/document/d/1lg9Mm1BqH4WhbXcVXY_-P0okXGXEfvPGg9HsAX6LwVE/edit?tab=t.gbd2zlj9qewe)
[CIVICS Committee (Intersect) Meeting - 2026/03/19 12:50 GMT - Recording](https://drive.google.com/file/d/10Ma1hFwzT0C9gzbm0Qs3aDDEKQRP9CWR/view)
## Agenda Items
* Updates and Housekeeping
* Committee Election Discussion
* Virtual Hub (VH) and X-spaces
* Working Group Updates
* Guest Discussion: Committee Minimum Size
## Decisions/Actions
The CIVICS Committee meeting covered updates on partner chain governance and technical hard fork status. Key discussions included finalizing working group deliverables and a significant recommendation to reduce the Constitutional Committee (CC) minimum size from seven to five to enhance governance resilience. Consensus was reached to proceed with this recommendation, while emphasizing a desired actual committee size of seven or more members.
### Decisions Made
Constitutional Committee Minimum Size Reduction: Consensus was confirmed to move forward with the recommendation from the Parameter Committee and TSC to reduce the Constitutional Committee (CC) minimum size from 7 to 5. This aims to prevent governance stalling due to a single resignation, with the understanding that the desired actual committee size should remain 7 or more.
CAP Editors' Roles and Guidelines Ratification: The CAP working group finalized CAP editors' roles and guidelines, which have met quorum in favor of ratification and are expected to be ratified next week.
### Action Items
NS: Reach out to KO for assistance publishing the educational resources knowledge base on the service kit.
LM: Check with Simo regarding when claimants should expect payment release times.
LM: Add confirmed committee election X space dates and links into documents. Send out calendar invites to individual members for the April 14th space.
KH: Help ensure the requested clarification on Constitutional Committee min size meta text is included in the parameter update.
Parameter Committee: Discuss the optimal timing of the Constitutional Committee min size governance action relative to the Plutus cost model update this evening.
## Topic Notes
| Topic | Discussion | Notes |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| 1. AS Departure | AS said farewell to the committee, with the committee thanking them for their service. | AS departed. |
| 3. Agenda Review & ISC Update | Agenda included updates, elections, VH, X-spaces, working groups, and CC min size. KO provided ISC update, noting high attendance. | Agenda reviewed. ISC update given. |
| 4. TSC & Hard Fork Status | TSC is working on parameter updates. Awaiting node 10.7 for hard fork status, followed by a new sync version. | Budget/params in progress. Node 10.7 awaited. |
| 5. Product Group & Town Square | Members discussed a partner chains X-space and a successful Town Square meeting. LM noted Town Square as a good experiment. | X-space, Town Square successful. |
| 6. Partner Chains & Governance | Discussion on partner chains X-space. KH suggested effective constitutional governance of partner chains as a group role. | Partner chain governance discussed. |
| 7. Transparency of Governance | LM confirmed Intersect is developing a renewed website section to clarify future governance actions and roadmap for community transparency. | Website to detail governance roadmap. |
| 8. Open Source Office & Next Meeting | KO announced DS will preview Beyond MVG data at the next Civics meeting. | DS to present next. |
| 9. Committee Election X-Space & VH | Confirmed dates for Committee Election X-spaces and VH sessions (March 31, April 7, April 14). Civics members requested for April 2nd and April 14th. | Election X-spaces and VH sessions set. Civics on April 2nd and April 14. |
| 10. CAP Working Group Update | TL reported CAP editors' roles/guidelines finalized, met quorum, and expected ratification. Discussions started on transition from CAPs to governance action. | CAP roles ratified. Process for CAPs. |
---
# 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-19th-march-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.