> 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-07-10-2024.md). # Weekly Catchup \[07/10/2024] ### Agenda * Updates since last meeting * Hurricane Update ### Notes The Budget Committee held its weekly catchup on October 7, 2024. Key points discussed include: 1. Committees have submitted their budget pieces, with final numbers from IO expected in 1-2 days. 2. The focus for the upcoming week is on preparing the presentation for DReps in Dubai. 3. Voting for committee seats is ongoing, with socialization efforts underway. 4. A proposed survey to collect information for future budget iterations was discussed further. Suggestions were made to improve its effectiveness, including adding role/domain questions for better data segmentation. 5. The 2025 budget draft document is in progress, with plans to consolidate multiple presentations into a single unified presentation for the DReps. 6. Approval was given to share current budget information with observers. 7. A quote for camera operators in Dubai was approved. 8. The committee discussed the need to review and approve the presentation slides for Dubai collectively. 9. Updates on managing ADA and finances were provided, with documentation on the process expected by the end of the following week. 10. Discussions touched on supporting startups and companies within the ecosystem, particularly regarding follow-on funding and increasing utility of ADA. The meeting concluded with plans for asynchronous votes on presentation slides and updates on hurricane preparations affecting one member's location. --- # 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-07-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.