# 12th March 25

The TSC did not achieve quorum and therefore no official decisions were taken. Instead a general discussion took place which is summarised below: 

## Attendees:

<table data-header-hidden><thead><tr><th></th><th width="187"></th><th></th><th></th></tr></thead><tbody><tr><td>Name</td><td>Attendance</td><td>Role</td><td>Voting Seat</td></tr><tr><td>Kevin Hammond</td><td>No</td><td>TSC Chair (IOE)</td><td>Yes</td></tr><tr><td>Adam Dean</td><td>No</td><td>TSC Vice-Chair</td><td>Yes</td></tr><tr><td>Markus Guffler</td><td>Yes</td><td>TSC Member (Cardano Foundation)</td><td>Yes</td></tr><tr><td>Johnny Kelly</td><td>Yes</td><td>TSC Member</td><td>Yes</td></tr><tr><td>Ben Hart</td><td>Yes</td><td>TSC Member (MLabs)</td><td>Yes</td></tr><tr><td>Neil Davies</td><td>Yes</td><td>TSC Member (PN Solutions)</td><td>Yes</td></tr><tr><td>Nicholas Clark</td><td>Yes</td><td>TSC Member (Tweag Modus)</td><td>Yes</td></tr><tr><td>Duncan Soutar</td><td>No</td><td>TSC Secretary</td><td>No</td></tr><tr><td>Matt Davis</td><td>No</td><td>Intersect - Tech Ops Lead</td><td>No</td></tr><tr><td>Christian Taylor</td><td>No</td><td>Intersect - Opensource Head</td><td>No</td></tr><tr><td>Terence ‘Tex’ McCutcheon</td><td>Yes</td><td>OSC Secretary</td><td>No</td></tr><tr><td>Abbie Yeates</td><td>Yes</td><td>Intersect - Delivery Assurance</td><td>No</td></tr><tr><td>Ricky Rand</td><td>Yes</td><td>IOE General Manager - Observer</td><td>No</td></tr><tr><td>Duncan Coutts</td><td>No</td><td>Welltyped - Observer</td><td>No</td></tr><tr><td>Lawrence Clarke</td><td>No</td><td>Intersect - Head of Core Services</td><td>No</td></tr></tbody></table>

**Minutes**

<table><thead><tr><th width="151">Topic</th><th width="308">Discussion</th><th>Action Items</th></tr></thead><tbody><tr><td>1. Management Contract Update</td><td>- Abbie's management contract is progressing well.<br>- Roles and responsibilities for Genesis rollout are being defined.<br>- Focus on stakeholder engagement before finalizing plans.</td><td>- Invite Abby to provide a formal representation at the next meeting.<br>- Finalize the roles and responsibilities chart for the Genesis rollout.</td></tr><tr><td>2. TSC Points to Intersect Board</td><td>- TSC's unanimous concerns about recent proposals were presented to the board.<br>- Concerns about lack of authority<br>- Emphasis on the need for legitimate processes.</td><td>- Await the board's official response to the TSC's points.<br>- Adam Dean to represent the TSC at the ad hoc meeting with the board.</td></tr><tr><td>3. Concerns About Proposed Changes</td><td>- Proposed changes seen as a radical shift in TSC scope.<br>- Concerns about the executability of the proposed approach.<br>- Fear that the changes could negatively impact Cardano in the long term</td><td>- Seek clarification on the proposed changes and their implications.<br>- Evaluate the TSC's future role and scope.</td></tr><tr><td>4. Reaction from Other Committees</td><td>- Other committees have expressed similar concerns and requested clarity.<br>- Concerns about the speed and lack of consultation in decision-making.</td><td>- Compile a list of all committees' concerns for the board.<br>- Seek a formal explanation for the rapid decision-making process.</td></tr><tr><td>5. Impact on Intersect Membership</td><td>- Concerns that the changes devalue Intersect membership.</td><td>- Address concerns about the impact on membership value.<br>- Reiterate the importance of member involvement in decision-making.</td></tr><tr><td>6. DREP Involvement and Responsibilities</td><td>- Discussion on the appropriate role of DREPs in decision-making.<br>- Concerns about the increased workload for DREPs.<br>- Proposal to have DREPs elect TSC members.</td><td>- Clarify the DREPs' responsibilities and workload.<br>- Explore the feasibility of DREPs electing TSC members.</td></tr><tr><td>7. Technical Competence and Authority</td><td>- Emphasis on the TSC's technical expertise and its importance.<br>- Concerns about losing the ability to reject or amend proposals based on technical suitability.<br>- Emphasis on the need to maintain control over technical delivery.</td><td>- Reiterate the TSC's need for authority in technical matters.<br>- Ensure the TSC's role in technical assessment and delivery.</td></tr><tr><td>8. Budget Responsibility</td><td>- Discussion on shifting budget responsibility away from the TSC.<br>- Concerns about the TSC's lack of core competency in budget management.<br>- Proposal to return to the TSC's original focus on technical assessment.</td><td>- Explore options for reallocating budget responsibilities.<br>- Focus the TSC's efforts on technical assessment and delivery.</td></tr><tr><td>9. Communication and Transparency</td><td>- Concerns about a lack of clear communication and transparency.<br>- Requests for meeting minutes and a list of complaints.<br>- Concerns about the "we have heard you" public statement.</td><td>- Demand greater transparency from the Intersect executive.<br>- Request access to meeting minutes and complaint lists.</td></tr><tr><td>10. Finding a Workable Solution</td><td>- Emphasis on the need for a practical and executable solution.<br>- Desire to ensure the changes benefit the Cardano community.</td><td>- Continue to work towards a solution that benefits the community.<br>- Ensure any changes are legally sound and sustainable.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/meeting-minutes/2025-tsc-meeting-minutes/12th-march-25.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.