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

# Civics Committee Minutes 11th June 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         | No         | 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     | 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/11 14:57 CEST - Recording](https://drive.google.com/file/d/15l9zB3aeH1JBhIt_Yyfcqs_FIlZx2a9S/view)

[CIVICS Committee (Intersect) Meeting - 2026/06/11 14:57 CEST - Notes by Gemini](https://docs.google.com/document/d/1Qsl2p-meo7U51yaOPyY2hwmZJu4tyuxPoFIfFXHhGDY/edit?tab=t.e5gzp3dprqo7)

#### Agenda Items

* Intersect Steering Committee (ISC) and Service Reward Policy Updates
* CAP Working Group: Phase Transition Vote
* Core Civics Strategic Planning (Q2 Achievements & Q3/Q4 Reporting)
* Code of Conduct & Minimum Viable Compensation Framework for the CC
* Governance Stakeholder Incentivization Models (Long-Term vs. Short-Term)

#### Decisions/Actions

**Decisions Made**

* CAP Public Beta Transition Approved: The committee voted unanimously 7–0 to transition the Constitutional Amendment Process (CAP) tool from closed internal testing into an Intersect-owned repository for broader public testing .
* Service Reward Policy Loop Closure: The ISC officially voted to extend the current committee service reward protocol deadline from June 2026 to December 2026, aligning the window to offset initial deployment delays from late last year .
* Long-Term Incentive Packaging: The committee agreed that future permanent structural compensation designs for the Constitutional Committee (CC) must be strategically packaged alongside DRep incentive systems to resolve broad ecosystem participation friction holistically .

**Action Items**

* TL: Convene the technical review call with backend developers to finalize domain hosting and migration parameters for the public CAP portal repository .
* NC & TL: Synthesize the committee's verbal brainstorming session into the formalized Intersect Q2 reporting and Q3 prioritization template .
* The Group: Review and post inline comments on the draft CC Code of Conduct and short-term compensation document before next week's cross-committee review .
* KE: Coordinate a session to formally present the technical architecture of the open SPO signature derivation improvement proposal (SPO Calidus keys) to the committee .
* S (Seomon): Incorporate IUR peer feedback to condense the core governance stake incentivization framework ahead of its presentation slot next week .
* TL: Maintain open commenting access on the temporary 75 million ADA stake pool loan proposal to gather detailed risk assessments across the channel .

#### Topic Notes

| Topic                     | Discussion                                                                                                                                                                                    | Notes                                                                                                             |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| 1. ISC Updates            | <p><br></p><p>NC outlined discussions from the ISC regarding reforms to the reward framework. The current system will extend through December 2026 to ensure complete coverage.</p>           | Interested members are invited to join the internal Intersect Governance Working Group.                           |
| 2. CAP Tool Transition    | After thorough internal iterations, the portal is ready to shift into public beta under the Intersect domain . This step officially moves the project from build Phase 2 to testing Phase 3 . | Admin or editor privileges can be requested via backend Stake IDs.                                                |
| 3. Incentives Mapping     | <p><br></p><p>S transferred the stakeholder initiative mapping registry into a centralized spreadsheet to organize future community outreach.</p>                                             | Cooperation has been secured with IOG research units to assist with peer-reviewed data modeling .                 |
| 4. Quarterly Evaluation   | <p><br></p><p>NC reviewed Q2 milestones, citing metadata coordination for the minimum CC size parameter reduction and the automated portal migration .</p>                                    | <p><br></p><p>NS clarified that the educational database architecture was completed during Q1 tracking .</p>      |
| 5. Strategic Priorities   | <p><br></p><p>JD urged giving top structural priority to a sustainable compensation template before ongoing budget cycles re-silo ecosystem attention .</p>                                   | <p><br></p><p>BA advised dedicating focus to open communication networks to slow down active DRep attrition .</p> |
| 6. Operational Efficiency | <p><br></p><p>KE presented an infrastructure request allowing SPOs to sign network protocol votes via derived keys rather than exposing cold security hardware .</p>                          | This item is tracked under a pending improvement statement authored by Martin Long .                              |
| 7. CC Code of Conduct     | <p><br></p><p>NC introduced an accountability architecture requiring explicit conflict disclosure, immediate rationales, and peer-to-peer metric reviews .</p>                                | The short-term framework suggests a reward of $250 in ADA per valid on-chain vote .                               |
| 8. Staking Loan Concept   | <p><br></p><p>TL pitched an experimental temporary loan program requesting a 75 million ADA withdrawal to saturate a designated administrative stake pool .</p>                               | Rewards (20,000–30,000 ADA per epoch) would fuel an active portal for compliant DReps and CC members .            |
| 9. Feasibility Analysis   | <p><br></p><p>NC raised concerns regarding legal licensing loops, transmitter liabilities, and the likelihood of large DReps blocking multi-million ADA withdrawals .</p>                     | <p><br></p><p>S supported trying the approach, pointing to the value of having a committed driver behind it .</p> |

<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-11th-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.