> 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/archive/2024-updates/october-monthly-update/weekly-catchup-01-10-2024.md). # Weekly Catchup \[01/10/2024] ### Agenda * Welcome New Observers * Updates since last meeting * Update on Draft Budget * Opens/Parking Lot ### Notes The committee discussed updates on budget preparation activities, including: * Documentation of processes and development of presentations for the upcoming Dubai event * Establishment of a secretary sync meeting for budget coordination * Presentation at the Intersect Steering Committee * Review of a budget survey to be released soon * Release of a Cardano 360 interview about the budget The current budget draft stands at 156 million ADA without including Project Catalyst numbers. There are still some outstanding items needed, including numbers from Project Catalyst and IOG Research. Discussion points included: * The need for alignment between different committees on processes and tooling * Plans for engaging with DReps (Delegate Representatives) about the budget * The contracting process, which will involve committee approval, core services review, and final sign-off by the CDF (Cardano Development Fund) * Plans for independent auditing of work performed under the budget Concerns were raised about potential inconsistencies if committees develop their own separate processes and tools. The importance of balancing decentralization with consistency was emphasized. The committee aims to have a more complete budget draft by October 21st for discussion with DReps. Outreach efforts to DReps are beginning, including through influencer channels and creation of explanatory videos and articles about budget processes. --- # 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/archive/2024-updates/october-monthly-update/weekly-catchup-01-10-2024.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.