> 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/the-fortunaway/project-overview/why-cultural-rwa.md). # Why Cultural RWA Most RWA narratives focus on financial assets such as treasuries, stocks, bonds, funds, or real estate. These use cases are important, but they are not the only way real-world value can enter the onchain world. Cultural RWA focuses on cultural value rather than financial return. For FortunaWay, Cultural RWA means using onchain infrastructure to make cultural participation more visible, verifiable, and connected. It allows users to build identity through learning, quests, credentials, contribution, and membership experiences. Cultural RWA is not about turning culture into speculation. It is about giving cultural participation a new digital identity layer. --- # 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/the-fortunaway/project-overview/why-cultural-rwa.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.