> For the complete documentation index, see [llms.txt](https://docs.wav-3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wav-3.com/welcome/quickstart/where-were-going.md). # Where We're Going Building toward agentic, merit-based music discovery WAV.3 is evolving into something much bigger than a referral-driven MVP. Without revealing specifics, our next phase focuses on: * **Virtuals Integration:** Partnering with Virtuals to power **agentic music discovery** — turning songs into autonomous AI agents that actively promote themselves post-graduation * **Anonymous Merit Discovery:** Moving from social clout to **purely merit-based discovery** — songs will launch anonymously and be judged on their sound alone * **Songs as Assets:** Each song will function as a **speculative on-chain asset**, with fans able to back tracks they believe in before anyone knows the artist. * **TasteGraphs:** As users listen, they build **TasteGraphs** that map their preferences, enabling highly personalized discovery and anti-farming protections This path will transform WAV.3 from a simple MVP into a **decentralized discovery engine** — one where human taste fuels the algorithms of the future. --- # 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.wav-3.com/welcome/quickstart/where-were-going.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.