> 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/tsc-decisions-log.md).

# TSC - Decisions Log

Decision Log of significant votes taken within Intersect's Technical Steering Committee

<table><thead><tr><th width="136">Category</th><th width="114">Date Closed</th><th width="324">Decision</th><th width="154">Link</th><th>Adam Dean</th><th>Ben Hart</th><th>Jonny Kelly</th><th>Kevin Hammond</th><th>Markus Gufler</th><th>Neil Davies</th><th>Nick Clarke</th></tr></thead><tbody><tr><td>TSC Cadence</td><td>6-Nov-24</td><td>Approval of creation of a vice-chair position within TSC</td><td></td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td></tr><tr><td>TSC Cadence</td><td>8-Nov-24</td><td>Vote for Kevin Hammond to act as chair of the TSC</td><td></td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td></tr><tr><td>Contracts</td><td>7- Nov -24</td><td>Decision to approve Hard Fork WG's recommendation not to initiate Chang 2</td><td></td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td></tr><tr><td>Contracts</td><td>4/12/24</td><td>Approval of final version of Outcomes and Deliverables of the Peras SoW with Tweag</td><td><a href="https://docs.google.com/document/d/1D2HRWg-yohwV_wP7IiUDgCmnNvM8ki_O7jpph7lptJU/edit?tab=t.0">Intersect Peras SoW</a></td><td></td><td>Approve</td><td>Approve</td><td>Approve</td><td></td><td>Approve</td><td>Abstain</td></tr><tr><td>TSC Cadence</td><td>15/11/24</td><td>Vote for Adam Dean to act as vice-chair of the TSC</td><td></td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td><td>Secret</td></tr><tr><td>TSC Cadence</td><td>3/12/24</td><td>Proposal to bring TSC forward 30 minutes and extend session to 90 minutes</td><td></td><td>Reject</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td></tr><tr><td>Hard Fork</td><td>11/12/24</td><td>Decision to approve the Hard Fork Working Group's Recommendation to submit a Governance Action to initiate the Plomin Hard Fork</td><td></td><td>Approve</td><td>Approve</td><td>No Vote</td><td>Approve</td><td>Approve</td><td>Approve</td><td>Approve</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>


---

# 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/tsc-decisions-log.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.