> 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/policies/evalution-criteria.md). # Evalution Criteria {% file src="/files/BqVFsf9g7rkn2RmOUegm" %} **Scope:** Continuity of Cardano **Definitions:** * Continuity is the unbroken and consistent existence or operation of something over time. * Cardano “Continuity” is defined as any approved technical services needed to build or fix current and future areas of the Cardano blockchain. * Continuity in this definition can include new development, such as the CIP-1694 governance software, upgrades to components or improvements in testing. To further help this definition we have outlined specific areas which would fall under consideration for TSC endorsement, funding and deliver: Cardano Maintenance, Cardano Development, Market Drivers and Appeal. At any given time the scope under delivery of the TSC will incorporate these elements. The total makeup of scope will vary over time, with those nearer the core having weighted priority. --- # 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/policies/evalution-criteria.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.