> 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/27-mar-24.md).

# 27 Mar 24

## **Attendees:** 

Duncan Soutar, Matt Davies, Kevin Hammond, Christian Taylor

## **Minutes:**

1. Parameter Committee - Requires a new secretary 
   1. Decision first see if anyone from the parameters committee is willing to put themselves forward as secretary at next meeting on 4th April
2. Outcomes of Parameter Committee Change Requests:
   1. Request to reduce min per bite - Recommended No Change (However this may be revisited post rollout of UTXO-HD) 
   2. Request to increase limits on transaction size to facilitate the running of larger DApps - Currently Under Review from IOI (Not that in future this should form part of a Change Process)
   3. Request to change Governance Parameters - Currently reviewing recommendations by the advisory group
3. Repo Migration
   1. TIS & LSM Tree migrated. Node Emulator & Intersect Address awaiting
   2. Issue raised that some repos don’t have maintainorships. Outsource with spread the ownership of these maintainors. Decision agreed that this should be done however Christian should draw up a risk management process.

## **Actions:**

* Kevin Hammond to share outcome of Governance Parameters review with the TSC when decision is made
* Kevin Hammond to share with the committee where the PI Sprints are edited within IOI
* Kevin Hammond to feedback results of requests for a new Secretary within the Parameters Committee 
* Matt Davis to provide more information on Backlog working group
* Christian Taylor to draw up a risk management process for selecting potential maintenance vendors
* Duncan Soutar to share Change Management 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/tsc-meeting-minutes/27-mar-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.