> 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/community/join.md).

# Join

### Join the RECORD Movement

Building the future of IP-native finance — together.

RECORD is more than a protocol — it’s a collective effort to reshape how intellectual property is valued, funded, and traded. Whether you’re a rights holder, developer, investor, or curious mind, there’s a role for you in our growing community. This is where music meets finance, where creativity becomes yield, and where culture becomes capital.

#### Choose Your Role, Join Your Path

| Role              | Join and Contribute                                                |
| ----------------- | ------------------------------------------------------------------ |
| IP Holders        | Raise capital: Join our Issuer Lounge and apply via form           |
| Investors         | Get updates: Subscribe to Telegram Alerts and follow us on X       |
| Developers        | Start building: Join the Discord Dev Hub, access docs, get support |
| Community Members | Participate: Vote, share, or propose ideas on Snapshot and GitHub  |


---

# 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/community/join.md?ask=<question>&goal=<endgoal>
```

`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.