> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/initiatives/decode.md). # MOSIP Decode MOSIP Decode is a virtual hackathon designed to encourage contributions to MOSIP’s open source platform from the **student community**! As a globally-recognised Digital Public Good, MOSIP strives to create inclusive and trustworthy digital identity systems for rapidly developing countries. Countries adapt MOSIP with the help of local experts to customise the platform to suit their requirements, but these needs are diverse and have endless potential for solutions. **This is where MOSIP Decode comes in.** This hackathon offers participants the opportunity to learn from industry experts and propose solutions for national digital infrastructure that is currently being implemented in over 25 countries across Asia Pacific, Africa, and Latin America and the Caribbean. Develop code that aligns with MOSIP’s guiding principles of modularity, scalability, security, privacy, and open standards with no vendor lock-ins. Join our mission of Empowering Lives, One Unique ID at a Time. --- # 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.mosip.io/1.2.0/initiatives/decode.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.