> For the complete documentation index, see [llms.txt](https://catalyst-swarm.gitbook.io/governance-guild/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://catalyst-swarm.gitbook.io/governance-guild/our-team.md). # Our Team Meet the people who contribute to Cardano Governance Services ## Active members (alphabetical by first name) Jonathan Postnikoff (JP)\ Miroslav Rajh\ Stephen Whitenstall\ Tevo Saks\ Vanessa Cardui ## Advisors (alphabetical by first name) Andre Diamond\ Felix Weber\ Nadim Karam\ Nori Nishigaya\ Peter Wolcott ## Biographies ### Andre Diamond Experience : > has experience in small business operation and accounting. Joined the Catalyst Circle Admin team as treasurer in Nov 2021 and has expanded this role by starting the Treasury Guild alongside Miroslav to support projects in the Catalyst community as well. Currently using and documenting GitHub Actions to help automate some of the tasks in Catalyst Circle and treasury work. ### Felix Weber > Co Founder & Somehow leader at the Catalyst Swarm. Recruited the participating members as Treasurers, Facilitators & Secretaries to the Catalyst Circle in CCv1; since then, supporting & advising the Team on its way forward. Fulltime Cardano & Catalyst Community Member since Fund 3, CCv1, CCv3 Member. > > Linkedin: > > Twitter: > > Dework: ### Jonathan Postnikoff (JP) - * Linkedin: * Twitter: > Experience : JP has been a member of the Cardano Community since December 2020 and has been active in Catalyst since Fund4. Originally beginning as a Swarm member, JP became a proposal assessor (previously CA) during F5 and has participated as both a PA and vPA in all subsequent funds. JP has also fulfilled the CC Admin Team’s secretary role since the election of CCv2, and is a funded proposer in F6 and F7 in support of the Circle and admin team. On a professional level, JP is a policy advisor in a federal bureaucracy and has a Master’s degree in public policy and public administration. His strongest skills include meeting secretarial services, one-on-one and group facilitation, proposal drafting, editing, and ideation support, and community engagement. Services : JP is available for governance services, administrative services, project management services and innovation ideation. ### Miroslav Rajh Experience : > 20 years of experience in managing finances and organizing the business of NGOs and the University. He also worked as a Human Resources Manager (HRM). Joined the Catalyst Circle Admin team together with Andre as treasurer in Nov 2021. Currently he is recording, documenting and managing all transactions for CC Admin Team, Swarm, Cardano4Climate, Community Governance and Bridge Builders. ### Nadim Karam * Linkedin: > Experience: Nadim is an enterprise consultant in the blockchain space; specializing in DAOs, DeFi, and decentralized identity. Nadim graduated from MIT Sloan School of Management in Blockchain Technologies: Business Innovation & Application. Within the Cardano ecosystem, Nadim is part of the Catalyst Circle Admin Team and runs a mission-driven stake pool. Nadim also manages ‘Cardano Middle East’, the largest Cardano community in the MENA region. Services: Nadim is available for governance services, meetings and workshop facilitation, ideation sessions, election management, and strategic consultations. ### Nori Nishigaya * Linkedin: * Twitter: > Experience : ​​Nori Nishigaya is the Founder of the Salmon Nation Decentralized Alliance (SANADA) and co-founder of Bridge Builders. He is a current member of the Catalyst Circle Admin Team since it’s inception, core team member of Cardano4Climate, a Cardano Ambassador, PA, and Funded proposer. He is passionate about radical inclusivity and community and devoted to making Cardano the best community on the planet. Nori brings over 30 years of experience in software development, agile methodologies, leadership in managing teams, and founding and running technology startups. His current passion is discovering governance and organizational best practices for radically decentralized and self-managed communities through experimentation and hands on practice. Services : ### Peter Wolcott Linkedin: Twitter: Linktree: Experience : Services : ### Stephen Whitenstall Experience : Co Founder of [QA-DAO](https://qadao.io/) ; Circle V2 representative for funded proposers. Funded proposer in Funds 5 to 10.\ Linkedin: ### Vanessa Cardui **Artist; archivist; activist.** Community engagement professional with 20+ years' experience supporting communities to take ownership of their own archival record.\ Part of [QA-DAO](https://qadao.io/); part of CGO (Community Governance Oversight); founding member of[ The Facilitators’ Collective](https://thefacilitatorscollective.wordpress.com/). ### Tevo Saks **Building Communities**\ Connecting Decentralised Open Source Services and Contributing to Community Governance Documentation {% embed url="" %} About me and recent related projects {% endembed %} --- # 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://catalyst-swarm.gitbook.io/governance-guild/our-team.md?ask=&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.