> For the complete documentation index, see [llms.txt](https://info.techup.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.techup.live/admin-instructions/tooling-and-software/tooling-claims-instructions.md). # Tooling Claims Instructions Each participant will be allocated a budget on tooling required for TechUp (e.g. to purchase domain name, CDN). The exact amount has been communicated ### DTC colleagues: HC colleagues have helped to raise the AOR collectively. You should submit your claims using the guide attached in the first admin email sent to you on 27 Mar 2024. ### IMDA colleagues Jaslyn has raised the AOR on your behalf, please approach her for queries on claims. ### MCI (including NAIG) colleagues Rachel Lim is your POC for all tooling-related claims. Please approach her for any queries. ### GOVTECH and all other colleagues You should raise your own AOR for the necessary tooling requirements. A sample AOR has been attached in the first admin email sent to you that you can use to adapt to your own needs. --- # 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://info.techup.live/admin-instructions/tooling-and-software/tooling-claims-instructions.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.