> 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-31st-2026-budget-comm-minutes.md). # August 31st, 2026 Budget Comm Minutes **Budget Committee Weekly Meeting — August 31st, 2026** **Date:** August 31, 2026\ **Time:** 13:00 UTC **Attendees:** Megan Hess (Chair), Kristijan Kowalsky (Vice Chair), Can Huzmeli, Eric Helms (SCATDAO), Fanny Wijaya, Ken-Erik Ølmheim (Observer), Nicolas Cerny, Rodrigo Pacini, Christina Gianelloni (SME), Lorenzo Bruno (Observer), Simo Simovic (Acting Secretary) **Quorum:** Confirmed (7 voting members present) ### 1. Opening Simo Simovic opened the meeting, confirmed quorum, and outlined the main agenda items. It was also noted that the committee's meeting facilitation should transition more clearly to the Chair, supported by the Secretary. A short preparation call between the Chair, Vice Chair, and Secretary was proposed to agree the agenda ahead of future meetings. ### 2. Update on the 2027 Budget Process An update was provided on internal discussions regarding Intersect's potential role in the next budget cycle. A first draft approach was being developed and would be discussed internally and with key ecosystem stakeholders. Early thinking included structuring funding around domains or categories and potentially defining percentages of the Net Change Limit for each domain. The proposed direction would involve close coordination between the Budget Committee and Product Committee, while also engaging other committees, DReps, vendors, Cardano Foundation, Input Output, and wider ecosystem stakeholders. Members discussed Intersect's possible role as a facilitator of this process rather than independently defining the strategy or funding allocation. The committee also highlighted the importance of beginning work soon, given the limited time remaining before 2027. ### 3. Priorities for the 2027 Budget Process Members discussed what the Budget Committee could begin working on even while broader strategic discussions remain ongoing. There was agreement that the existing operational process for proposal submission, review, voting, and on-chain execution worked relatively well and could be refined rather than completely redesigned. The larger challenge was identified as the work that comes before proposal submission: defining ecosystem priorities, determining how resources should be allocated, and establishing an appropriate Net Change Limit. Members emphasized that the NCL should not simply be treated as a maximum spending figure. It should ideally be connected to strategic priorities and a more structured approach to treasury allocation. The committee agreed that work on the next cycle should begin, while remaining flexible enough to incorporate the wider ecosystem strategy as it develops. ### 4. Q4 Planning The committee discussed preparations for Q4 planning. Given the uncertainty around the 2027 Budget Process, members agreed that the Budget Committee's Q4 plan could initially remain high level and be updated once there is greater clarity on Intersect's role and the broader ecosystem approach. The committee plans to dedicate time during the next two weekly meetings to developing the Q4 plan. Lorenzo Bruno will support the committee with planning activities during the Acting Secretary's upcoming absence. ### 5. Committee Member Experience Survey Members were asked to complete the Committee Member Experience and Performance Review survey. It was clarified that members serving on multiple committees should select all relevant committees and answer based on their overall experience, using the open-text questions to highlight any significant differences between committees. The survey forms the first stage of a broader feedback process, which is expected to include focus groups and individual interviews. ### 6. September Focus Period The committee discussed the proposed focus period during the final two weeks of September. The purpose is to give committees additional time to complete actions and planning work, while also reducing meeting load during the final week of the quarter when Chairs and Vice Chairs will participate in quarterly review sessions. The committee agreed to pause its regular weekly meetings on **September 21 and September 28**. During the final week of September, the Chair and Vice Chair will participate in quarterly sessions to present Q3 achievements and the Q4 plan. ### 7. Final Review of Vision 2030 and KPI Feedback The committee continued reviewing its draft feedback on the Vision 2030 KPI framework. Members reaffirmed the importance of strengthening the connection between the long-term vision, annual priorities, treasury funding, and measurable outcomes. The committee also supported adding questions regarding ownership of strategic pillars and KPIs, including who is responsible for achieving goals and who measures progress. Further discussion focused on economic sustainability and the importance of understanding the cost of operating and maintaining Cardano before determining how the NCL could be allocated across other strategic priorities. Members discussed the difficulty of defining these costs from scratch and suggested that historical spending from the previous budget cycle could provide a practical starting point. There was also support for distinguishing maintenance costs from new development and growth initiatives when considering future funding allocations. ### 8. Historical Spending and Funding Domains The committee discussed using previous treasury-funded proposals to better understand how spending could map to future funding domains. Once an initial set of domains is available, historical approved proposals could be categorized against those domains to estimate how much funding has previously been allocated to each area. This analysis could provide a practical baseline for future discussions on budget allocation rather than starting entirely from theoretical figures. Existing categories used in the 2025 budget cycle may also be reviewed as an initial reference point. ### 9. Actions and Next Steps * Continue stakeholder discussions on the proposed approach for the 2027 Budget Process. * Begin high-level Q4 planning and refine it as further strategic direction becomes available. * Dedicate time during the next two committee meetings to Q4 planning. * Committee members to complete the Committee Member Experience survey. * Cancel the regular Budget Committee meetings on September 21 and September 28. * Finalize the Budget Committee's Vision 2030 and KPI feedback and share it with the Product Committee. * Add feedback on the importance of understanding Cardano's operating and maintenance costs. * Review previous budget categories and use historical proposal data as a starting point for future domain and funding-allocation discussions. --- # 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-31st-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.