> 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/09-17-2026-meeting-minutes.md). # (09/17/2026) Meeting Minutes ## Attendees:
NameAttendanceRoleVoting Seat(Y/N)Term
Sebastian PabonYesChairYOctober 2025
Kambale Mechack ElieYesVice ChairYApril 2026 (2y)
Terence β€˜Tex’ McCutcheonYesSecretaryNN/A
Bernard SibandaNoMemberYOctober 2025
Jordan HillNoMemberYOctober 2025
Udai SolankiNoMemberYOctober 2025
Reshma MohanYesMemberYOctober 2025
Pawel JakubasYesMemberYApril 2026 (2y)
Olivier MwatsimulamoYesMemberYApril 2026 (2y)
Bora ObenYesMemberYApril 2026 (2y)
Community/Other Attendees * Harun Mwangi * Ian McCullough **Recording:** [Open Source Committee (Intersect) - 2026/09/17 - Recording](https://drive.google.com/file/d/1CQP-CtgubjKoEwAci49dyzUVYDd6l-NU/view?usp=sharing) **Transcript:** [Open Source Committee (Intersect) - 2026/09/17 - Transcript](https://docs.google.com/document/d/14M1bJrC4suEK69yReHbtTc21dpgID9E-WgINfVLYIgk/edit?usp=sharing) **Chat Transcript:** [Open Source Committee Meeting – 2026/09/17 – Chat Transcript](https://drive.google.com/file/d/1MPtKPVm3dBgzwaF7OwbWRSquqiZ-xr_C/view?usp=sharing) ## Intros Bora: TBD Bernard: OSC - voting member Dominik: Open Source Committee Member, part of Inferara. Jordan: TBD 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 9.17.26 * 1694.io * Cella - rewrite * Cella vs other AI Tooling for CC * DA Q2 Report * Open Forum ## Decisions/Actions **Decisions** * **Review Process for Cella Statement of Work:** The Committee decided to conduct the detailed review of the revised Cella proposal asynchronously by leaving direct inline comments and observations on the uploaded document in Google Drive rather than making an immediate approval decision. **Actions** * **Terence McCutcheon:** * Ping committee members in a few days to a week to check on their progress with reviewing the Cella SOW document. * Invite Darlington to the next committee meeting to present the 1694.io proposal. * Finalize and publish the Developer Advocate Q2 Closeout Report before the end of September. * **Committee Members:** * Review the revised Cella SOW in Google Drive and leave inline comments and feedback regarding timeline, cost breakdowns, and technical concerns. * Review the Developer Advocate Q2 Closeout Report draft and add suggestions/comments to strengthen weak sections (Sebastian agreed to review a portion of the document). * **Harun Mwangi:** * Forward the Africa Tech Summit sponsorship request/proposal to for review by the Intersect events team. | Topic | Discussion | Notes | | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Welcome & Meeting Overview | Terence opened the meeting and acknowledged he was a bit out of his element and lacking a detailed agenda. Darlington was expected to present regarding 1694.io but had not yet joined. |


| | Chella Statement of Work Revision | Terence shared a link to the revised Cella Statement of Work (SOW) in Discord. The initial proposal was previously declined, leading Ian to submit a revised version with reduced funding ($33,000) and an extended 21-week timeline (about 5 months). | Terence uploaded the document to the drive and shared the revised link in Discord. | | Chella Proposal Document Review | Sebastian suggested taking five minutes to review the Cella SOW directly in the meeting. Terence shared his screen, highlighting the three main milestones: vote witnessing/transaction assembly, rationale anchoring and constitutionality review, and self-hosting for non-technical committees. | The timeline effectively extended by two-thirds compared to original expectations. | | Chella Value & Criticality Debate | Bora questioned whether Cella incubates entirely new software versus supporting established tooling with an existing user base. Terence explained the funding program supports both established tools and critical new infrastructure that the ecosystem relies upon (e.g., Constitutional Committee/DRep tooling). Bora noted the Constitutional Committee already functions without it and expressed concerns over arbitrary pricing and day counts. | Committee members were asked to leave inline comments and questions directly on the document in Google Drive. | | AI Tooling Comparison (Deliberate CC vs. Chella) | Olivier reviewed a recently announced AI tool (Deliberate CC) and compared it to Chella. He noted Deliberate CC uses multiple AI models to assist with deliberation and decision-making, whereas Cella focuses on structured, verifiable on-chain transaction building and vote witnessing. | Olivier and Bora agreed both tools serve different layers of the governance workflow rather than directly competing. | | Governance Ecosystem References | Bora highlighted existing Cardano governance platforms listed on cardano.org/app and DRepTalk, pointing out that certain proposed features may already exist elsewhere in the ecosystem without requiring new funding. | Bora encouraged the committee to review ecosystem directories before making funding decisions. | | 1694.io Retooling Application | Terence shared the original application intake form for 1694.io in Discord. The proposal focuses on retooling and maintaining the site to educate the community and improve DRep discovery. | Darlington was unavailable to present due to a scheduling conflict. | | Evaluation of 1694.io Submission | Bora argued that several statements in the 1694.io submission were exaggerated, as it is not the only DRep discovery or voting tool in the ecosystem. He noted that while the platform has historical value, its features have been surpassed by newer tools like GovTool and CIP-179 implementations. | Terence plans to invite the proposer to a future meeting to clarify details. | | Chella Author Q\&A with Ian | Ian joined the call to answer questions about Cella. In response to Bora's inquiry about reaching out to target users, Ian confirmed he discussed the tool with Mike Hornan and received feedback regarding credential handling. | Ian offered to collect formal written feedback or fold user testing into Milestone 1. | | Developer Advocate Q2 Closeout Report | Terence presented the DA Q2 report draft and thanked Olivier for compiling initial data. Bora reviewed the linked GitHub evidence and noted that some onboarding proof appeared weak (e.g., simple README edits rather than substantive code contributions). Terence agreed, explaining that tighter PR/commit metrics will be required in Version 3 of the program. | Committee members were asked to assist in reviewing and refining individual milestones before the end of September. | | Developer Advocate Title Retention | In response to a query from 8pro, Terence clarified that former developer advocates retain their titles after their 9-month term ends. While funding ends with the term, advocates are encouraged to remain active community helpers. | Advocates continue to serve as extended representatives in the Cardano ecosystem. | | Event Sponsorship Inquiry | Harun, speaking as a developer advocate, asked if Intersect or the Open Source Office could sponsor the upcoming Africa Tech Summit in February 2027. | Terence advised directing event sponsorship requests to as the committee does not currently have an unallocated event budget. | | Intersect Governance Working Group & Meeting Adjournment | Terence reminded the committee of the Intersect Governance Working Group meeting taking place immediately following the call, focusing on committee reform and governance processes. | Terence adjourned the meeting and reminded members that internal Discord channels remain open for async feedback. | --- # 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/09-17-2026-meeting-minutes.md?ask=&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.