> 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-9th-july-2026.md).

# Civics Committee Minutes 9th July 2026

#### Attendees

<br>

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td>Name</td><td>Attendance</td><td>Role</td><td>Voting Seat (Y/N)</td><td>Election Term</td></tr><tr><td>Nicolas Cerny</td><td>Yes</td><td>Chair</td><td>Y</td><td>April 2028</td></tr><tr><td>Larisa Mcfarlane</td><td>Yes</td><td>Intersect</td><td>N</td><td>N/A</td></tr><tr><td>Megan Dyamond</td><td>Yes</td><td>Member</td><td>Y</td><td>October 2026</td></tr><tr><td>Thomas Lindseth</td><td>Yes</td><td>Secretary</td><td>N</td><td>N/A</td></tr><tr><td>Ken-Erik Ølmheim</td><td>Yes</td><td>Member</td><td>Y</td><td>April 2028</td></tr><tr><td>Simon Fleck</td><td>Yes</td><td>Member</td><td>Y</td><td>October 2026</td></tr><tr><td>Ian Hartwell</td><td>Yes</td><td>Member</td><td>Y</td><td>October 2026</td></tr><tr><td>Musa Ridwan Itopa</td><td>Yes</td><td>Member</td><td>Y</td><td>October 2026</td></tr><tr><td>Beatrice Anihiri</td><td>Yes</td><td>Member</td><td>Y</td><td>April 2028</td></tr><tr><td>Jose Miguel De Gamboa</td><td>Yes</td><td>Member</td><td>Y</td><td>April 2028</td></tr></tbody></table>

\ <br>

#### Agenda Items

* Intersect Steering Committee (ISC) and Board Election Requirements
* Constitutional Committee (CC) Election Hydra Blockers
* Working Group Progress: CAP Alpha Launch and Guides
* Technical Constitutional Amendment Strategy for Ouroboros Leios

#### Decisions/Actions

**Decisions Made**

* Incentive Presentation Deferral: The committee agreed to defer the revised stakeholder governance incentive presentation to next week's session to allocate full focus to immediate parameter amendment strategies.
* Time-Critical CC Election Promotion: Due to visibly low early voter turnout, the committee designated the manual amplification of current DRep voting links as a high-priority outreach action across all standard member profiles.
* Leios Constitutional Amendment Integration: The committee decided to leverage the newly built CAP portal as the official deployment test ground for the upcoming Ouroboros Leios parameter guardrail update, keeping the code modification strictly bounded to technical scope.

**Action Items**

* NC: Share the official Intersect Budget Committee feedback collection form link within the internal communication channel.
* NC: Update next week's meeting schedule to ensure dedicated presentation time for the governance incentive proposal.
* S (Seomon): Circulate the condensed and optimized stakeholder incentive framework draft ahead of next week's call.
* LM & TL: Publish the verified DRep voting status updates and promotional text links in the team chat to coordinate amplification.
* TL: Complete and publish the step-by-step end-user process documentation guides for the upcoming CAP alpha environment.
* Carlos Lopez de Lara: Partner directly with the parameters committee to finalize specific protocol guardrail metrics and compile the formal Leios text.
* Carlos Lopez de Lara: Revise and update immediate operational timelines to remain completely compliant with the strict 90-day on-chain constitutional socialization deadline before the targeted September 11 submission window.
* KE & Carlos Lopez de Lara: Sync offline to finalize deployment strategy and address lingering governance concerns ahead of the targeted hard fork timeline.
* The Group: Access the Intersect member dashboard area to study the updated bylaws texts and cast ballots in the active vote event.

#### Topic Notes

<br>

| Topic                 | Discussion                                                                                                                                                                                                                   | Notes                                                                                                                                                      |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Board Criteria     | The group reviewed strict eligibility parameters for upcoming Intersect board seats. Candidates require completed KYC, full membership status for at least 180 continuous days, and historical committee service experience. | Active sitting board members remain fully eligible to seek re-election.                                                                                    |
| 2. Hydra Interruption | Technical issues on the backend Hydra node framework are actively blocking live vote submissions for the CC election.                                                                                                        | Engineers expect a permanent resolution to deploy today; the hard deadline is fixed for July 23.                                                           |
| 3. Alpha Delivery     | TL noted that backend staging for the CAP public alpha environment is firmly on track for an end-of-July rollout.                                                                                                            | To minimize confusion, user documentation and walkthrough guides will be released incrementally.                                                           |
| 4. Ouroboros Leios    | The impending Ouroboros Leios upgrade requires a formal amendment to the Cardano constitution to introduce updated performance guardrails.                                                                                   | The on-chain action is scheduled for September 11 (Epoch 655) to secure critical technical capabilities ahead of the fork.                                 |
| 5. Strict Scope Caps  | The committee emphasized that the Leios text must remain strictly restricted to technical network parameters.                                                                                                                | Keeping the draft clear of social or contentious governance rule revisions makes it the perfect non-disruptive test case for the new portal.               |
| 6. Compliance Locks   | Carlos Lopez de Lara pointed out that any major constitutional change is constrained by a rigid 90-day off-chain socialization requirement.                                                                                  | Engineering paths must be tightly synced immediately to ensure the finalized draft meets this timeline constraint without delaying the hard fork schedule. |

<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-9th-july-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.
