> For the complete documentation index, see [llms.txt](https://spozz-club.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spozz-club.gitbook.io/whitepaper/2.-vision-and-mission.md). # 2. VISION AND MISSION **Vision** SPOZZ envisions a world where music has real value — not just for middlemen and big platforms, but for the creators who bring it to life and the fans who breathe energy into it. We see a music economy that is fair, social, and direct — where artists and audiences connect without intermediaries, share in success, and shape the future of the platform together. SPOZZ aims to turn today’s $30B streaming industry into a $100B+ creator-driven music economy — open, global, and built on shared ownership. **Mission** Our mission is to empower creators and fans by providing the tools, platform, and governance structure needed to reshape the music industry from the ground up. SPOZZ exists to: * Deliver fair compensation for creators * Foster direct artist-fan relationships * Enable transparent rights licensing * Create a community where value and voice are shared * Use blockchain as an infrastructure, not a gimmick We’re here to build a future-ready platform that makes being a musician — or a music fan — more rewarding in every way. --- # 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://spozz-club.gitbook.io/whitepaper/2.-vision-and-mission.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.