> For the complete documentation index, see [llms.txt](https://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://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-committees/technical-steering-committee-tsc.md). # Technical Steering committee (TSC) {% hint style="info" %} View more details in the dedicated Committee space [technicalsteeringcommittee.docs.intersectmbo.org](https://technicalsteeringcommittee.docs.intersectmbo.org/) {% endhint %} ## What is the Technical Steering Committee? The Technical Steering Committee ensures that the governance of Cardano is based upon sound technical awareness and best practices. ## Why is this committee important? The Technical Steering Committee provides expert technical guidance to support Cardano's development. By bringing together key developers, suppliers, and third parties, the committee advises on contract arrangements and service level agreements, creates technical proposals, and evaluates community submissions like parameter updates and hard forks, ensuring technical decisions are well-informed and sound. ## Which topics does this committee cover? Takes a leading role in defining and advising on Cardano continuity development to support the Cardano network, including contracts and agreements with Intersect members. It’s a highly technocratic committee, providing deep technical analysis and advice to ongoing development projects, parameter settings (through the Parameter Committee (PC)), and any other network related conditions. ## How to join? The TSC participates in Intersect committee elections to select the next cohort of members. Intersect always communicates details on how to apply and vote well in advance of each election. *** --- # 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://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-committees/technical-steering-committee-tsc.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.