> 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/archive/cardano-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/constitutional-convention-voting-tool/expectations.md). # Expectations {% hint style="danger" %} **ARCHIVED** This page has been archived. It's content might be outdated. {% endhint %} ## What a tooling provider can expect: In addition to the above requirements (which amount to features to be exhibited by the tooling), we (the people assessing the RFP responses) will want to know how people applying for funding to build this tool intend to develop this product, e.g. testnet/ development environments, and how their team intends to test the tooling as they develop it. We will require that the team write, follow and maintain a test plan. We will also be interested in how the team intends to deploy their tooling and will expect some sort of deployment of features that have been developed from the first milestone. A representative of the team selected to build the Constitutional Convention voting tool will be required to attend a standup meeting with representatives of Input | Output (IO) between one and three times per week to report on progress and ensure a smooth delivery. ## Notes The above requirements assume that: 1. We build tooling 2. The tooling is built by a community member and utilises the blockchain. Ultimately we could decide to go with an established web 2.0 solution to achieve the same voting experience. It may be decided that paper ballots are feasible, Regardless these will be prepared in case of technical failure during the convention. The deadline for having the tooling built, tested and deployed is 15th November 2024 \\ --- # 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://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/constitutional-convention-voting-tool/expectations.md?ask=&goal= ``` `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.