> 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/governance.md). # Governance The RECORD ecosystem is structured around two key entities, each dedicated to distinct yet complementary roles, enabling clarity, accountability, and scalability within the ecosystem. #### The Association (RECORD) * Type: Not-for-profit Association (Verein) * Role: Governance, Ecosystem Stewardship, Research RECORD Verein acts as the non-profit steward of the ecosystem, responsible for strategic direction, governance, regulatory compliance, and the maintenance of open and decentralized infrastructure. Its mission includes ensuring ecosystem transparency, managing public-good initiatives, and guiding the decentralised evolution of RECORD’s blockchain infrastructure and token economy. #### The Advisory Company (RECORD Partners) * Type: Private Advisory & Structuring Firm * Role: IP Deal Origination, Due Diligence, Market Facilitation RECORD Partners serves as the institutional advisory firm, bridging IP owners (artists, labels, rights holders) with institutional and retail investors. It is responsible for sourcing, structuring, and underwriting royalty-based financial products. By maintaining rigorous due diligence and professional standards, RECORD Partners ensures high-quality investment opportunities, driving adoption and scaling the ecosystem. #### Dual-Entity Structure This governance model balances decentralization and market efficiency, aligning mission-driven stewardship with professional financial market standards. It ensures RECORD Nexus remains accountable, transparent, and equipped for institutional adoption while progressing towards decentralization and community-driven governance. --- # 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/governance.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.