> 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-product-committee/policies/cardano-vision-workshops-reimbursement-limits.md). # Cardano vision workshops reimbursement limits All the amounts above are guidance which the product committee can decide to override with an explicit decision as long as overall the costs remain within the budget approved. The product committee will prioritise local product experts where possible or those who would be traveling regardless. The product experts approved by the product committee to travel will need to be mindful of keeping expenses to the minimum required. Where possible the product committee should aim to run more than one workshop with the same product experts in the same region. Below are the guide max amounts: * Travel costs should be claimed to up to $2000 per product expert (this is the max amount of long flights. Economy is recommended where possible) * Lodging costs and other expenses should be claimed to up to $1500 * Product expert could decide to ask for stipend for the workshop day of up to $500 For workshop organization * $1500 for workshop venue rent * $1000 for workshops food and refreshments --- # 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-product-committee/policies/cardano-vision-workshops-reimbursement-limits.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.