> 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-17th-2026-budget-comm-minutes.md). # August 17th, 2026 Budget Comm Minutes **Budget Committee Weekly Meeting — August 17th, 2026** **Date:** August 17, 2026\ **Time:** 13:00 UTC **Attendees:** Megan Hess (Chair), Kristijan Kowalsky (Vice Chair), Can Huzmeli, Eric Helms (SCATDAO), Fanny Wijaya, Nicolas Cerny, Rodrigo Pacini, Stephen Wood, Christina Gianelloni (SME), Musa Ridwan Itopa (Observer), Seun Gbiri (Observer), Simo Simovic (Acting Secretary) **Quorum:** Confirmed (8 of 10 voting members present) ### 1. Opening Simo Simovic opened the meeting, confirmed quorum, and outlined the main agenda items: reviewing the Product Committee's Cardano 2030 KPI survey and continuing discussion on the Budget Process retrospective and direct DRep outreach. The committee was reminded that the KPI survey was intended to collect a consolidated response from each committee rather than individual submissions from members. ### 2. Review of the Cardano 2030 KPI Survey The committee reviewed the Product Committee's request for feedback on the Cardano 2030 KPIs and discussed how relevant the existing framework is to the Budget Committee's remit. Members broadly agreed that the Budget Committee is not responsible for directly delivering ecosystem-level KPIs such as adoption, transactions, active wallets, or TVL. Instead, the committee's potential role is more closely related to supporting accountability around treasury-funded initiatives and ensuring that funded proposals can demonstrate progress against the KPIs they committed to. Treasury and network economics were identified as the areas most closely connected to the committee's work. The discussion also highlighted the need for clearer ownership of ecosystem KPIs. Members questioned who is responsible for driving progress against the targets, monitoring delivery, and ensuring that KPI-related work leads to practical outcomes rather than remaining primarily a strategic document. ### 3. Economic Sustainability and KPI Framework The committee discussed whether the Cardano 2030 framework should include stronger measures related to long-term economic sustainability. Members suggested that treasury inflows, transaction fees, reserves, network operating costs, and the sustainability of incentives should be considered when defining long-term targets. The committee also questioned how some of the existing KPI targets had been established and suggested that future KPIs would be more useful if supported by an economic model explaining the assumptions behind the targets and how they contribute to network sustainability. There was general support for providing this type of broader feedback to the Product Committee rather than attempting to answer every survey question where the Budget Committee has limited relevance. ### 4. Budget Committee Feedback to the Product Committee The committee agreed that completing the KPI survey directly may not be the most effective way to communicate its feedback. Instead, members supported preparing a short document summarizing the committee's main observations, including: * The need for clearer ownership and accountability for ecosystem KPIs. * The importance of linking funded proposals to measurable outcomes and monitoring whether those outcomes are achieved. * The need for stronger economic rationale behind network and treasury-related KPI targets. * The importance of ensuring that strategic KPIs are connected to practical priorities, funding decisions, and implementation. The Acting Secretary agreed to prepare a short draft based on the discussion and bring it back to the committee for review before submitting feedback to the Product Committee. ### 5. Preparing for the 2027 Budget Process The discussion broadened into the committee's role in preparing for the next budget cycle. Members emphasized that work on the 2027 Budget Process should begin soon, but that greater clarity is needed regarding Intersect's role, the Board's expectations, and the committee's mandate before significant design work is undertaken. There was support for exploring a more structured approach to treasury funding, potentially using categories, domains, or funding buckets. However, members noted that the committee should not independently determine ecosystem priorities or how much funding should be allocated to each area without broader strategic direction. The committee also discussed the importance of understanding its own role and mandate before developing the next process, particularly in relation to treasury stewardship, financial risk, oversight, and advisory responsibilities. An upcoming discussion with Intersect leadership and the Board was expected to provide greater clarity on strategic direction and the committee's role in the 2027 Budget Process. ### 6. Budget Process Retrospective and DRep Outreach The committee revisited the retrospective effort and the limited number of responses received through the existing survey. A shared outreach tracker had been created to coordinate direct engagement with DReps. Committee members were asked to add their names next to DReps they could contact. Members agreed that stakeholders should not be required to complete the full survey if they prefer a more direct conversation. Feedback could instead be collected through short calls, emails, or individual discussions and summarized in the shared document. The committee discussed preparing two or three simple questions focused on the 2026 experience and what stakeholders would like to see improved in 2027. Members also supported reaching out to additional stakeholders, including DReps from different regions and individuals or organizations that had significant involvement in ecosystem governance or treasury discussions. ### 7. Actions and Next Steps The following next steps were identified: * Prepare a short Budget Committee feedback document on the Cardano 2030 KPI framework and bring it back for review. * Seek further clarity from Intersect leadership and the Board on the committee’s role in the 2027 Budget Process. * Continue discussion on potential improvements to the 2027 Budget Process once strategic direction is clearer. * Committee members to add their names to the DRep outreach tracker. * Finalize a short set of questions for direct DRep outreach. * Continue collecting feedback from DReps and other relevant ecosystem stakeholders on the 2026 process and improvements for 2027. --- # 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-17th-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.