> 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/19th-june.md).

# 19th June

## **Attendees:** 

Duncan Soutar, Matt Davies, Kevin Hammond, Christian Taylor, Abbie Yeates, Lewis Mayne

### Minutes:

1. Parameters Committee

   1. Plutus cost model to be revisited on nect call
   2. Governance parameters for 1694 now agreed
   3. MinFeeRespit per bite - feedback that setting could be too high and so will be revisited at next call as looking for sustainability for DApps

2. Opensource Requests

   1. Looking into rewards & recognition for contributors
   2. Security policy does not require boards approval - will set up and start running
   3. Kevin & Christian to determine whether Nix website comes under Intersect or not
   4. Framework for opensource projects passed
   5. Engineering Handbook to be forked over to Intersect

3. Update from Hard Fork Working Group

   1. Timeline Reviewed and updated - well received by the group
   2. Hard Fork Timeline to be simplified and published to the community
   3. Ecosystem readiness to be shared at next session - will call out what exchanges and apps are expected to do
   4. Kevin Hammond to review timing

4. Change Requests

   1. No new change requests

5. Security Council

   1. No update

6. TSC Development

   1. Update on first session with the TSC Development group. 
   2. 5 Initial elected roles have been defined with responsibilities allocated: Continuity Seat, Quality Seat, Research Seat, Programme Seat & Operations Seat


---

# 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/19th-june.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.