> 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-budget-committee/committee-meeting-notes/2026-meeting-notes/budget-committee-weekly-meetings/august-10th-2026-budget-comm-minutes.md). # August 10th, 2026 Budget Comm Minutes **Budget Committee Weekly Meeting — August 10th, 2026** **Date:** August 10, 2026\ **Time:** 13:00 UTC **Attendees:** Megan Hess (Chair), Kristijan Kowalsky (Vice Chair), Nicolas Cerny, Eric Helms (SCATDAO – briefly attended), Simo Simovic (Acting Secretary), Alexandre Maaza (Cardano Foundation – Guest), Can Huzmeli, Musa Ridwan Itopa (Observer), Thomas Lindseth (Observer) **Quorum:** Not confirmed in the meeting transcript (four voting members reported at the opening). ### 1. Opening Simo Simovic opened the meeting and welcomed attendees. The primary agenda items were a presentation from the Ecosystem Funding Working Group under the Product Committee, coordination of stakeholder outreach for the 2026 Budget Process retrospective, and discussion of the Product Committee's KPI survey. The Chair agreed to include the Ecosystem Funding Working Group presentation as an additional agenda item. ### 2. Ecosystem Funding Working Group Presentation A representative from the Cardano Foundation presented an initiative led through the Ecosystem Funding Working Group under the Product Committee, aimed at developing a more coordinated and strategic approach to ecosystem funding. The initiative is funded by the Cardano Foundation as a public good and explores how different funding mechanisms can better align with Cardano 2030 objectives. The project includes an assessment of Cardano's existing funding landscape, stakeholder interviews, and the development of an initial ecosystem funding framework. The proposed framework focuses on four key areas: * **Domain-based allocation:** Structuring funding around strategic priorities and funding categories. * **Builder accessibility:** Improving visibility and connections between builders and funding opportunities. * **Return and recoverability:** Considering the financial sustainability and effectiveness of treasury funding. * **Layered KPIs:** Establishing measurable outcomes at ecosystem, funding domain, and project levels. The committee discussed the importance of measuring actual outcomes rather than only project deliverables, establishing accountability for monitoring results, and incorporating perspectives from successful builders and external industry experts. Members recognized that the research could provide valuable input into recommendations for the 2027 Net Change Limit (NCL) and improvements to the 2027 Budget Process. The committee was invited to review the published research and provide feedback through the consultation form by **August 21, 2026**. The final research deliverables are expected by the end of August, with further community engagement and collaboration to be discussed. ### 3. Budget Process Retrospective and Stakeholder Outreach The committee reviewed progress on expanding stakeholder engagement following the previous meeting's discussion about the limited number of retrospective survey responses. A shared outreach tracking spreadsheet was presented, containing a list of DReps and space for committee members to identify stakeholders they can contact. Members agreed that feedback should not be limited to formal survey responses. Direct conversations, emails, and individual calls could provide more meaningful insights, particularly from DReps and other stakeholders who may not complete the survey. The committee discussed developing a short set of questions to guide these conversations, focusing on: * **Process timing:** When the 2027 Budget Process should begin and whether a more continuous or quarterly approach would be beneficial. * **Funding categories:** Whether treasury funding should be structured into thematic categories or funding buckets. * **Process improvements:** What should be started, stopped, or continued based on the 2026 experience. Members also discussed approaching organizations and proposal submitters that did not participate in the 2026 Budget Process to understand their reasons and identify improvements that could encourage participation in future cycles. Timing was highlighted as a significant concern, particularly where funding requirements do not align with the budget process schedule. The committee agreed that a common outreach approach and a concise set of questions should be developed before members begin contacting stakeholders. The possibility of establishing measurable outreach targets was also raised. ### 4. Planning for the 2027 Budget Process The committee briefly discussed how retrospective feedback and the Ecosystem Funding Working Group's research could inform preparations for the next budget cycle. Members emphasized the importance of determining when the 2027 Budget Process should begin, noting that stakeholder feedback on timing could provide valuable evidence for discussions with the Board and Intersect. The committee also recognized the need to move beyond collecting feedback and begin considering how the findings could translate into practical improvements. A more detailed discussion was deferred to a future meeting when additional committee members could participate. ### 5. Product Committee KPI Survey The committee briefly discussed the Product Committee's request for feedback on the Cardano 2030 KPIs. It was clarified that the Budget Committee is expected to provide one consolidated response representing the committee's collective views, rather than individual submissions from each member. The committee agreed to review the survey questions in advance and discuss its feedback at the next meeting. ### 6. Actions and Next Steps The following next steps were identified: * Share the Ecosystem Funding Working Group materials with Budget Committee members. * Committee members to review the research and provide feedback by August 21. * Continue coordination with the Ecosystem Funding Working Group on how the research could inform the 2027 Budget Process. * Share the DRep outreach tracker and ask members to identify stakeholders they can contact. * Develop a short set of questions for direct stakeholder outreach. * Continue collecting feedback from DReps, proposal submitters, and other relevant stakeholders. * Share the Product Committee KPI survey materials for review. * Continue discussion on the 2027 Budget Process and KPI feedback at the next meeting. --- # 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-budget-committee/committee-meeting-notes/2026-meeting-notes/budget-committee-weekly-meetings/august-10th-2026-budget-comm-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.