> 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-25th-june-2026.md).

# Civics Committee Minutes 25th June 2026

#### Attendees

| Name                  | Attendance | Role      | Voting Seat (Y/N) | Election Term |
| --------------------- | ---------- | --------- | ----------------- | ------------- |
| Nicolas Cerny         | No         | Chair     | Y                 | April 2028    |
| Larisa Mcfarlane      | Yes        | Intersect | N                 | N/A           |
| Megan Dyamond         | No         | Member    | Y                 | October 2026  |
| Thomas Lindseth       | Yes        | Secretary | N                 | N/A           |
| Ken-Erik Ølmheim      | Yes        | Member    | Y                 | April 2028    |
| Simon Fleck           | No         | Member    | Y                 | October 2026  |
| Ian Hartwell          | Yes        | Member    | Y                 | October 2026  |
| Musa Ridwan Itopa     | Yes        | 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/06/25 14:58 CEST - Notes by Gemini](https://docs.google.com/document/d/1v0cgHPsvBA51XJX0K68-44b9eFOLz6Om-QeW9yxY88g/edit?tab=t.9twjcadttp1g)

#### Agenda Items

* Intersect Steering Committee (ISC) & Technical Steering Committee (TSC) Updates
* Constitutional Committee (CC) Size Change Parameter Voting Status
* Working Group Progress: CAP & Governance Incentives
* Q3 Planning, Priority Alignment & Communications
* Calidus Keys Voting Educational Briefing
* Intersect Virtual Hub Event Coordination
* Governance Ecosystem Tooling Realities (GovTool & Eternal Wallet)
* Constitutional Committee (CC) Candidate Pipeline and Verification

#### Decisions/Actions

**Decisions Made**

* SPO Calidus Keys Voting Deferral: Due to multiple committee members requesting more time to read background materials, the committee deferred the endorsement vote for ledger-level Calidus key integration to the next formal meeting.
* GDPR Strategy for CAP Tool: The committee agreed to omit email alerts in the first version of the Constitutional Amendment Process (CAP) tool to circumvent complex GDPR privacy delays and keep deployment on schedule.
* Commitment to Monthly X Spaces: The committee rejected a weekly broadcast cadence in favor of committing to one high-value monthly X Space focused on engagement, education, and hosting external guests.
* Ecosystem Event Prioritization: The committee decided to prioritize leveraging upcoming Intersect Virtual Hub rooms for time-sensitive CC election pitches and CAP demos over an immediate Kaledus key focus.

**Action Items**

* S & KE: Coordinate asynchronously to address low attendance patterns in the Governance Incentives Working Group and assess alternative scheduling blocks.
* JD: Track the release of the impending Intersect rewards policy overview report authored by Lorenzo and report back to the group for feedback.
* BA & LM: Collaborate directly to map out the tactical 12-week communication template for Q3 utilizing Intersect's shared social infrastructure.
* BA & TL: Connect with outside engineers (such as Martin Lang) to gauge technical slot requirements for future virtual hub sandbox presentations.
* TL & Mike: Finalize administrative credential vetting for the three late-registering CC candidates before the weekend verification cutoff.
* The Group: Access the community blog post shared by BA to review the operational and technical trade-offs of SPO hot signature derivations.

#### Topic Notes

| Topic                  | Discussion                                                                                                                                                    | Notes                                                                                                                                     |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Parameter Vote      | KE presented on-chain metrics for the minimum CC size reduction action, tracking at 41.48% out of a required 75% approval floor.                              | TL noted that several large DReps commanding over 100 million ADA are giving favorable feedback but have not yet voted.                   |
| 2. CAP Specifications  | TL reported ongoing back-end infrastructure prep to get the portal fully hosted within a week or two.                                                         | Stake-weighted on-chain proposal signaling has been earmarked as an architecture request for future versions.                             |
| 3. Incentives Health   | The incentives working group failed to find a quorum this week as several members experienced direct calendar scheduling conflicts.                           | NS committed to aligning with Simon to restructure the meeting block to recover lost participant momentum.                                |
| 4. Structural Scarcity | JD advocated for a lean "less is more" strategy focus for Q3, advising the committee to divide limited, unfunded hours across two highly critical priorities. | BA highlighted that a record intake of 10 distinct candidate profiles has successfully expanded the pipeline for the CC election.         |
| 5. Broadcast Strategy  | LM pointed out the difficulty of sustaining empty weekly schedules. BA noted that a single, tightly consolidated monthly broadcast prevents exhaustion.       | The committee will actively cross-participate in native community spaces such as Cardano Over Coffee and Epoch End.                       |
| 6. Calidus Security    | KE, IH, and BA explained to the group that Calidus keys serve as a "hot ID card" authorized by an air-gapped cold passport key.                               | If a hot wallet profile is ever compromised, it can be immediately rotated without putting underlying core pool signatures at risk.       |
| 7. Tooling Casualties  | JD raised concerns over breaking connection changes inside the new Eternal Wallet update that prevent voting on non-CLI platforms.                            | TL and LM confirmed GovTool is frozen in status quo maintenance with zero bug-fixing support after falling victim to a lack of funding.   |
| 8. Vetting Infractions | TL flagged that two CC applicants generated critical security assets in hot, online configurations, rendering their cold credentials invalid.                 | Unverified profiles will be disqualified and dropped from the final Ekklesia voting pool if they fail to regenerate keys cleanly on time. |

<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-25th-june-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.
