> 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-technical-steering-committee/meeting-minutes/2025-tsc-meeting-minutes/19th-mar-25.md).

# 19th Mar 25

The TSC held a session for Voting Members Only. 

Topics of discussion were: 

* **Discussed concerns over the new budget process:**
  * The TSC expressed their concerns over the new budget process. Including how developers will be held accountable, how technical oversight will be conducted, how interacting proposals will be coordinated as well as the potential bureaucracy involved.
  * They critiqued the lack of clarity on how value for money will be evidenced, the potential for conflicting proposals, and the absence of clear accountability.
  * A central issue is the disconnect between responsibility and authority. The TSC argues that they cannot be held accountable for project outcomes if they lack the authority to influence project selection and management.
* **Technical Roadmap and Budgeting:**
  * The TSC discusses the importance of maintaining a clear and stable technical roadmap.
* **Legal and Reputational Risks:**
  * The TSC members discuss the potential legal liabilities associated with the proposed processes, particularly concerning bribery and corruption.
* **Communication:**
  * The group agreed to draft a public statement on concerns they have on new budget process


---

# 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-technical-steering-committee/meeting-minutes/2025-tsc-meeting-minutes/19th-mar-25.md?ask=<question>&goal=<user_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.