> 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-parameter-committee/about/committee-members/roles-and-responsibilities.md).

# Roles and Responsibilities

{% hint style="info" %}
This page is written on behalf of the Parameter Committee, the information contained is subject to change and amendment by the committee chairs at any time and should be used at your own risk
{% endhint %}

## Criteria for Committee Roles

### Chair/Vice-Chairs

* Detailed knowledge of the Cardano ecosystem and node implementation
* Understanding of the effect of each protocol parameter on Cardano's operation
* Technical expertise across all areas: technical/security, network, economic, and governance
* Proven ability to lead and manage complex technical discussions
* Ability to resolve technical conflicts
* Capacity to ensure consensus among committee members

### Advisory Group Chairs

* Expert understanding of Cardano
* Expert knowledge in the relevant area (technical/security, network, economic, or governance)
* Ability to lead the advisory group
* Skill in collecting and distilling technical discussions within the group
* Capacity to represent the area in open discussion with other committee members

### Domain Experts

* Strong engagement within and knowledge of the relevant domain (SPO, DApp, etc.)
* Ability to represent the concerns of the domain in technical protocol parameter discussions
* Engagement in following and participating in technical discussions across different areas

## Parameter Committee members

* The Governing Board may appoint a chairperson (or “Chair) and a vice-chair, or it may choose to delegate responsibility for selecting or electing a chair to the committee or subcommittee.
* Committee members will be appointed by the chairs along technocratic/meritocratic lines.
* Only members of Intersect are eligible to apply to participate as members in the Parameter Committee and its subcommittees.

## About our key committee members&#x20;

<table><thead><tr><th width="219">Name</th><th width="323">Brief summary and experience</th></tr></thead><tbody><tr><td>Kevin Hammond</td><td>Kevin is Head of Engineering (Cardano Core) at IO Engineering. He has a background in (distributed) performance analysis, safety and security. He has led the Cardano Core Development team through 8 hard forks (from Shelley to Chang), and has a detailed knowledge of the Cardano node and its on-chain operation.</td></tr><tr><td>Markus Gufler</td><td>Markus has 25 years of experience in ISP business, IT infrastructure, networking and monitoring. He has been and is active in many areas of the Cardano ecosystem, as a developer, facilitator, consultant and stake pool operator. In the Cardano Foundation, he helps to mediate between the technically oriented community and the various teams and projects in the Foundation.</td></tr><tr><td>Alexander Moser</td><td>Alex is the Associate Head of Infrastructure at Cardano Foundation. Previously, he set up custodial and non-custodial security systems for banks across 19 different blockchains and led the institutionalization of staking as a financial instrument in Switzerland. His knowledge of and insights into various ecosystems eventually brought him to Cardano.</td></tr><tr><td>Vijayanath Bhuvanagiri</td><td>Vijay is the CTO at EMURGO, he led the revamp of Yoroi wallet architecture. Vijay is currently leading the technical effort for launching USDA stable coin on Cardano blockchain.</td></tr><tr><td>Neil Davies</td><td>Neil consults on system performance, networking and design-for-maintenance. He has a background in large scale distributed systems and systems deployed in adversarial settings. He has been advising Cardano since 2017 contributing to the networking, node architecture and deployment.</td></tr><tr><td>Samuel Leathers</td><td>Sam is Head of Product for IO Engineering. He has been involved in Cardano since the Byron days and led the way through multiple hard forks wearing many hats. He now works directly with the development teams on prioritizing features going into cardano-node. While not having an economic background, he has lots of experience with the economic parameters of Cardano and the contention between them from working with pools since the Shelley era.</td></tr><tr><td>Adam Rusch</td><td>Adam is a Teaching Assistant Professor of Information Sciences at the University of Illinois at Urbana-Champaign , where his research and teaching focus on the ways that people use information and communications technology to organize into groups and communities that build together. He has been involved in the Cardano community since 2018 and was a Founding Core Contribute to ADAO and co-founder of Summon Platform. As a member of Intersect he has served on the Community Advisory Board, Civics Committee, and Parameters Committee, where he led the Governance Parameters Working Group.</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 dynamically by asking a question.

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

```
GET https://committees.docs.intersectmbo.org/intersect-parameter-committee/about/committee-members/roles-and-responsibilities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
