> For the complete documentation index, see [llms.txt](https://docs.fortunaway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortunaway.com/core-products/fortuna-quest.md). # Fortuna Quest Fortuna Quest is the campaign and task engine of FortunaWay. It allows users to complete structured activities such as cultural learning, wallet connection, community engagement, content creation, event participation, feedback submission, and partner campaigns. Technically, Fortuna Quest includes three core layers: * **Task Layer**: defines quest type, rules, requirements, duration, and reward logic. * **Verification Layer**: checks whether the user action is valid through API data, manual review, wallet signature, social proof, or partner confirmation. * **Reward Layer**: issues Fortuna Points, Credentials, role progress, or campaign access after verification. Fortuna Quest is the main bridge between user activity and the FortunaWay identity system. --- # 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.fortunaway.com/core-products/fortuna-quest.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.