> For the complete documentation index, see [llms.txt](https://documentation.record.nexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.record.nexus/members/ecosystem-principles.md). # Ecosystem Principles W3M aims to revolutionise the music industry through decentralised digital technologies, fostering a dynamic community centred on connection, collaboration, and innovation. Key to the W3M experience is how it encourages members to demonstrate their commitment to the ecosystem as they make connections and collaborations. This concept is part of a multi-layered participation structure aimed at building a community of actively contributing members. Emotional intimacy is prioritised over economic intimacy, ensuring that early members become ambassadors who represent the ecosystem’s vision and values. Member motivations are crucial to W3M's membership experience, which is segmented into three stages: Discover, Involve, and Retain. The focus is on attracting members who are intrinsically motivated and aligned with W3M's objectives, thereby creating vibrant sub-communities contributing to the ecosystem. Trust is foundational to W3M, built through aligning organisational intentions with member values and goals. A point-based system rewards contributions, enhancing member loyalty and virality, eventually transforming them into co-creators of the ecosystem, thereby boosting its network effects. Three guiding principles steer W3M's actions: Connection and Collaboration, Trust and Commitment, and Emotional Intimacy over Economic Intimacy. By adhering to them, W3M aims to build an ecosystem where members can make connections, share a common purpose, and collaborate to develop blockchain solutions. --- # 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://documentation.record.nexus/members/ecosystem-principles.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.