> 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/products/record-notes.md). # RECORD Notes Royalty-Linked Notes (RLNs) are structured, tokenised financial instruments secured by future royalty revenues from IP. They provide rights holders with upfront capital in exchange for assigning their future royalty streams. #### Revenue-Backed, Not Debt-Based RLNs transfer economic rights to future royalties, differing fundamentally from traditional loans. Investors receive repayments directly linked to royalty performance from the revenue originating platforms. #### Built-In Legal Safeguards RLNs include critical investor protections: * Irrevocable Assignment: Economic rights fully transferred for the RLN term. * Bankruptcy Isolation: Protection against claims in issuer insolvency. * Enforcement Terms: Defined penalties triggered by issuer non-compliance, ensuring strong contractual protection. #### Dynamic Return Structure The innovative maturity structure aligns stakeholder incentives: * **Minimum Return Threshold**: Note maturity extends automatically if performance falls below set benchmarks, giving a protection to investors. * **Maximum Return Cap**: Early closure when returns exceed performance expectations, securing investor gains, reducing the friction for right holders. #### Due Diligence and Pricing Every RLN undergoes independent underwriting and third-party validation, ensuring transparent pricing, risk clarity, and consistency across the ecosystem. --- # 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/products/record-notes.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.