> 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/tsc-meeting-minutes/2nd-oct-24.md).

# 2nd Oct 24

Attendees: 

1. **Zendesk Team Level 1&2 Support - Migration to Intersect - Matt** 

   1. Discussion on potential for moving Zendesk team to Intersect to provide Level 1 & 2 support

2. **Election Nominations - Approval of Candidates Approach - Matt**
   1. No formal withdrawals of candidates
   2. Endorsement or not by the TSC will be clearly marked on candidate Application
   3. All candidates that have not been endorsed have been given opportunity to clarify their application and opportunity to make appropriate updates
   4. \[Action: Duncan] - Updates to TSC ToR to clarify roles and responsibilities of TSC Seats 

3. **Q4 Priorities of IOE - Duncan & Kevin**

   IOE presented list of priorities for Q4 for approval by TSC

   1. Main Priority: 
      1. Final delivery of CIP 1694 (Chang+1)
      2. Addressing Capacity and Scaling:
         1. Parameters, Security Improvements, UTxO-HD (Out of memory data storage), Ouroboros Genesis, potentially LMDB solution (with option to turn on or off)
      3. Continued Engagement: 
         1. Security Council, Technical Steering Committee, Hard Fork Committee, Open Source Committee 
      4. Prioritisation of New Work Items: 
         1. via Technical Working Groups, Technical Steering Committee, Roadmap Committee, …

\[Action: To be ratified as party of next week’s TSC]

\[Ratified offline in following days]<br>

4. **Review of Roadmap - Duncan**
   1. Amendments to Capacity - Reduced to 32L to bring down overall cost of budget
   2. Review Current Roadmap Items -&#x20;
   3. Risk on costs of coalition - discussion on expected average costs of developers
   4. Alignment to Product Committee - Action to review Product Committee Goals and align to roadmap proposals
   5. Leios - discussion on aims for 2025


---

# 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/tsc-meeting-minutes/2nd-oct-24.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.