> 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-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/10-01-2026-meeting-minutes.md).

# (10/01/2026) Meeting Minutes

## Attendees:&#x20;

| Name                     | Attendance | Role       | Voting Seat (Y/N) | Term            |
| ------------------------ | ---------- | ---------- | ----------------- | --------------- |
| Sebastian Pabon          | Yes        | Chair      | Y                 | October 2025    |
| Kambale Mechack Elie     | Yes        | Vice Chair | Y                 | April 2026 (2y) |
| Terence ‘Tex’ McCutcheon | Yes        | Secretary  | N                 | N/A             |
| Bernard Sibanda          | Yes        | Member     | Y                 | October 2025    |
| Udai Solanki             | No         | Member     | Y                 | October 2025    |
| Reshma Mohan             | No         | Member     | Y                 | October 2025    |
| Pawel Jakubas            | No         | Member     | Y                 | April 2026 (2y) |
| Olivier Mwatsimulamo     | Yes        | Member     | Y                 | April 2026 (2y) |
| Bora Oben                | No         | Member     | Y                 | April 2026 (2y) |

Community/Other Attendees

* Aleksandr Vershilov
* Daniel Mwihoti
* Darlington Wleh

**Recording:** [Open Source Committee (Intersect) - 2026/10/01 - Recording](https://drive.google.com/file/d/1U_dMjb-eMdxaCBeYlB4iKhT5T_Nc2TGM/view?usp=sharing)

**Transcript:** [Open Source Committee (Intersect) - 2026/10/01 - Transcript](https://docs.google.com/document/d/1G5y9R8sESMnvN7SQf10RDdAlkHsS66BS8nVDwqPsa58/edit?usp=sharing)

**Chat Transcript:** [Open Source Committee Meeting – 2026/10/01 – Chat Transcript](https://drive.google.com/file/d/1dZMQQMI8Nk5ITflw_GTfKpF_b9_YHKCX/view?usp=sharing)

## Intros

**Bora:** TBD\
**Bernard:** OSC - voting member\
**Kambale:** OSC Vice chair\
**Olivier:** Goma Hub Member, Milestone Reviewer-Project Catalyst, MCC and OSC\
**Pawel:** Member OSC, CF\
**Reshma:** OSC voting member\
**Sebastian:** OSC chair. Andamio co-founder.\
**Tex:** Open Source Program Manager, Intersect, OSC Secretary, Committee Member Advocate\
**Udai:** Member OSC, AIQUANT Technologies

## Agenda 10.01.26

* [1964.io](http://1964.io)
* Canonical ledger state
* KardanoSDK
* MeshAI
* Maintainer Retainer Program
* Open Forum

## Decisions/Actions

**Decisions**

* **No Formal Proposal Approvals Made:** Due to a lack of quorum (only 4 members present out of the required 5 for an 8-member committee), the Open Source Committee made no formal votes or binding approval decisions on any presented proposals during the meeting..
* **Request for Mesh AI Clarification:** The Committee ”present” decided to provide critical feedback on the Mesh AI Statement of Work and invite the project team to present at a future meeting before taking further action.

**Actions**

* **Aleksandr:** Share the presentation slides and submit final, concrete budget breakdowns (differentiating active development from maintenance work) for the Canonical Ledger State extension.
* **Aleksandr:** Post links to the repository, CIP-165, and previous proposal documentation in the chat.
* **Committee Members:** Review the detailed documentation and proposals on Google Drive / ClickUp for the Canonical Ledger State, 1694.io, Cardono SDK, and Mesh AI.
* **Darlington:** Explore collaboration and coordination with the GovTool team/maintainers regarding UI/UX distinction and feature integration.
* **Terence:** Compile meeting feedback, formulate polls/threads, and post them in Discord for the Committee to conduct asynchronous voting on the proposals and the Mesh AI Statement of Work.
* **Terence:** Facilitate the restarting of the GovTool working group in coordination with Sireto.

| Topic                                   | Discussion                                                                                                                                            | Notes                                                                                                                                                         |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Meeting Intro & Quorum Check            | Terence opened the Open Source Committee meeting for October 1st, 2026. The meeting lacked a quorum, but proceeded to accommodate guest presenters.   | Terence noted declinations, including one from Bora.                                                                                                          |
| Cardano Canonical Ledger State Overview | Aleksandr presented the Cardano Canonical Ledger State proposal, explaining its role as an interoperability format for node ledger state transfers.   | The project originated under Intersect proposals (2025–2026), with CIP-165 and reference tooling built for Haskell and Rust.                                  |
| Feature Gaps & Tooling Needs            | Aleksandr highlighted missing support for the Dijkstra era, alongside missing integration with Cardano CLI and snapshot converters.                   | Addressing these gaps is required before downstream adoption in Mithril can proceed.                                                                          |
| Project Scope, Timeline & Budget        | The proposal requests funding for 2–3 developer-months of feature work plus long-term maintenance.                                                    | Aleksandr estimated the total cost at $40,000–$50,000 (Band 0 cap), with exact figures to be finalized.                                                       |
| Documentation & Resources               | Committee members inquired about available project documentation and links.                                                                           | Aleksandr shared repository and CIP links in the chat, while Terence referenced the proposal files in ClickUp and Google Drive.                               |
| 1694.io Project Overview                | Darlington presented 1694.io, a community tool built to provide DReps with digital profiles, aggregated activity timelines, and metadata management.  | The site allows DReps to publish vote rationales and update profile metadata without manual GitHub interactions.                                              |
| Governance Expansion & Features         | Darlington detailed plans to expand 1694.io into full on-chain governance, integrating proposal tracking, direct voting, and CIP-179/CIP-079 support. | The platform aims to correlate on-chain governance with off-chain history across Catalyst, Intersect, and ecosystem funds.                                    |
| Ecosystem Alignment & GovTool           | Sebastian and Terence raised questions regarding 1694.io's alignment and potential overlap with GovTool.                                              | Darlington clarified that 1694.io focuses on broader social context and historical correlation, expressing openness to collaborating with the GovTool team.   |
| Cardono SDK Review                      | The committee reviewed a funding application for "KardanoSDK" submitted via ClickUp.                                                                  | Members noted a lack of demonstrated production usage, no active repository commits, and zero saved developer hours, comparing it to an early-stage proposal. |
| Mesh AI Statement of Work               | The committee evaluated the Statement of Work for Mesh AI, which covers three milestones per work package for a requested $15,000 USD.                | Members noted that details were unclear and suggested inviting the team to a future meeting for further clarification.                                        |
| Maintainer Retainer Program             | Terence introduced Daniel to share his experience with the Maintainer Retainer Program.                                                               | Daniel expressed gratitude for the learning opportunities and mentioned working on a concept to present soon.                                                 |
| Quorum & Discord Voting                 | Terence confirmed the committee size is now eight members, requiring a minimum of five votes for official decisions.                                  | Discussions and formal voting on the reviewed proposals and Statement of Work will take place asynchronously in Discord.                                      |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/10-01-2026-meeting-minutes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
