> 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-21st-may-2026.md).

# Civics Committee Minutes 21st May 2026

#### Attendees

| Name                  | Attendance | Role      | Voting Seat (Y/N) | Election Term |
| --------------------- | ---------- | --------- | ----------------- | ------------- |
| Nicolas Cerny         | Yes        | Chair     | Y                 | April 2028    |
| Larisa Mcfarlane      | Yes        | Intersect | N                 | N/A           |
| Megan Dyamond         | Yes        | Member    | Y                 | October 2026  |
| Thomas Lindseth       | Yes        | Secretary | N                 | N/A           |
| Ken-Erik Ølmheim      | Yes        | Member    | Y                 | April 2028    |
| Simon Fleck           | Yes        | Member    | Y                 | October 2026  |
| Ian Hartwell          | Yes        | Member    | Y                 | October 2026  |
| Musa Ridwan Itopa     | No         | Member    | Y                 | October 2026  |
| Beatrice Anihiri      | Yes        | Member    | Y                 | April 2028    |
| Jose Miguel De Gamboa | Yes        | Member    | Y                 | April 2028    |

#### Sources

[CIVICS Committee (Intersect) Meeting - 2026/05/21 14:58 CEST - Recording](https://drive.google.com/file/d/1ONsKdLSsRgoKy-kt2xBZyJELPiqw1_W4/view)

[CIVICS Committee (Intersect) Meeting - 2026/05/21 14:58 CEST - Notes by Gemini](https://docs.google.com/document/d/1pEGOCmPjcP8tK46DV86K5Q5CxXiwfBl4PjSMRDptZzY/edit?tab=t.ty1meu3qq6et)

#### Agenda Items

* Intersect Steering Committee (ISC) Updates
* Civics Committee Chair and Vice Chair Election Timeline
* Civics Budget Proposal Comments & Review
* Constitutional Committee (CC) Minimum Size Parameter Change Metadata
* Working Group Updates: CAP and Governance Incentives
* CC members Outgoing Member Interviews Framework

#### Decisions/Actions

**Decisions Made**

* Chair Election Timeline established: The application window for Chair and Vice Chair will open from May 21 to May 28, followed by a voting phase from May 28 to June 4.
* Asynchronous Budget comments: The committee decided to finalize responses to Hydra voting tool comments asynchronously in the internal channel due to the upcoming May 22 locking deadline.
* Joint Metadata Review: Rather than adjusting the stripped metadata back and forth, the committee decided to hold a joint meeting with the Technical Steering Committee (TSC) to finalize the text.
* CAP Portal Technical Shift: The CAP working group approved a major architectural transition away from GitHub Open Authorization to a dedicated database to align with Intersect's repository security constraints.

**Action Items**

* TL: Open the Chair and Vice Chair election registration portal and document the exact timeline in the internal channel.
* NC: Coordinate draft responses to feedback from DReps by tomorrow.
* NC: Reach out to the Technical Steering Committee regarding the removal of educational context from the CC min size change rationale.
* TL: Connect with the secretary of the TSC to schedule the joint metadata reconciliation call.
* S:: Build a tracking spreadsheet for governance initiatives and draft an promotional post for Intersect’s social media channels.
* JD & S: Share the finalized framework for Constitutional Committee interviews and collect volunteer reviewers.
* TL: Set up auto-recording and transcript features for the committee accounts to host the upcoming qualitative interview calls.

#### Topic Notes

| Topic                   | Discussion                                                                                                                                                                                                  | Notes                                                                                                                               |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| 1. ISC Updates          | NC shared updates regarding a draft dismissal policy centered on meeting votes rather than simple attendance, a stablecoin budget payout option, and the approval of an advisory Code of Conduct Committee. | Minutes for these updates are indexed on the ISC public knowledge base.                                                             |
| 2. Chair Elections      | Elections will take place via the Intersect members portal. To meet quorum, a minimum of six committee members (two-thirds) must cast votes.                                                                | Candidates will be allocated time during next week's meeting to present their strategies and roadmaps.                              |
| 3. Budget Strategy      | NC highlighted that while proposals lock tomorrow at 12:00 PM UTC, comments and answers from the official account can remain active until voting starts on May 26.                                          | KE recommended referencing secondary data from the Beyond Minimum Viable Governance report to reinforce target audience statements. |
| 4. CC Size Change       | The proposal alters the required on-chain minimum parameter from seven to five to provide operational buffer when members retire. Currently, single members hold extreme leverage.                          | IH noted that TSC edits stripped historical education points explaining why the previous parameter attempt failed.                  |
| 5. CAP Portal Status    | Moving to a dedicated database is 95% complete in testing, introducing roughly a one-week delay. Stake IDs can now be submitted for admin/editor tool roles.                                                | Dummy examples from the prior version must be hand-ported over before the public test phase.                                        |
| 6. Incentives WG        | S requested structured feedback on the master initiatives mapping document and outlined steps to convert these files into digestible sheets.                                                                | Call-out features will be cross-promoted inside upcoming Intersect email newsletters.                                               |
| 7. CC Member Interviews | JD and S compiled a qualitative 4-pillar feedback guide covering structural expectations, operational tooling blocks, systemic friction, and unspoken onboarding rules.                                     | This internal report will assist future budgets and establishes the framework for a decentralized governance database.              |

<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-committee-minutes-21st-may-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.
