> 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/april-29th-2026-budget-working-session-vote-record.md). # April 29th, 2026 Budget Working Session Vote Record Budget Committee 2026 Process Working Session — Vote Record > **Note:** Working-session minutes are not normally published. This record captures only the **attendance** and the **single voting action** taken during the session, per committee practice. *** ### Working Session — April 29th, 2026 **Date:** April 29, 2026 **Time:** 10:01 EDT **Attendees:** Eric Helms (SCATDAO), Jose Velazquez, Kristijan (Chris) Kowalsky, Lloyd Duhon (Secretary), Megan Hess (Chair), Nicolas Cerny, Otávio Lima, Simo Simovic (Project Manager) **Quorum:** Confirmed. *** ### Motion — Publish Budget Committee Budget Ask to Ecclesia for DRep Feedback **Motion:** Approve the release of the Budget Committee's 2026 budget ask to the Ecclesia framework tool so that DReps can begin providing feedback. * **Mover:** Jose Velazquez * **Second:** Eric Helms #### Discussion **Nicolas Cerny** noted he supported voting today but suggested the committee use the rest of the working-session time to make any final refinements before publication. **Lloyd Duhon** confirmed that any changes the committee directs over the coming weeks will be made to the document the same day they are requested — the document remains fully editable in Ecclesia after publication. **Lloyd** clarified the meaning of the vote: * **Yes** = Lloyd will copy the current contents into Ecclesia and submit it as a proposal draft, opening it for DRep feedback. * **No** = Wait; do not yet publish. He further confirmed that whatever form the document is in at the **end of today's working session** is what will be published. #### Roll Call Vote | Member | Vote | | -------------------- | ----------- | | Eric Helms (SCATDAO) | Yes | | Megan Hess | Yes | | Jose Velazquez | Yes | | Kristijan Kowalsky | Yes | | Nicolas Cerny | **Abstain** | | Otávio Lima | Yes | **Result:** **Motion carries** (5 Yes, 1 Abstain). The Budget Committee's 2026 budget ask will be published to Ecclesia following the close of today's working session, opening the proposal for DRep feedback. --- # 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/april-29th-2026-budget-working-session-vote-record.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.